# Tr(): rawnode() and rawleaf() support

**URL:** <https://delvingbitcoin.org/t/tr-rawnode-and-rawleaf-support/901>\
**Category:** Implementation\
**Tags:** taproot, miniscript\
**Created:** [May 22, 2024, 3:25pm UTC](https://delvingbitcoin.org/t/tr-rawnode-and-rawleaf-support/901 "2024-05-22T15:25:38Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ajtowns](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/ajtowns/32/417_2.png) [@ajtowns](https://delvingbitcoin.org/u/ajtowns)\
**Post date:** [May 28, 2024, 9:20pm UTC](https://delvingbitcoin.org/t/tr-rawnode-and-rawleaf-support/901/6 "2024-05-28T21:20:57Z")

</div>

> [@Eunovo](#):
>
> @sipa I wonder if you have any ideas about how N2KBs are supposed to be used. I imagine that other parties of the transaction will fear hidden spend paths.

Could be useful for inheritance/escrow type services: “this isn’t my money, so I don’t care about other spend paths, but in an emergency, the spend path I do know about can be used to help that person recover their money even if they’ve lost all their keys”.

Could be useful for places where you’re using multiple wallets for some funds – maybe your main wallet understands some super clever contracts that you want to put in a tapscript, but your backup (hardware? cold?) wallet doesn’t and can only spend via the key path; in that case all the backup wallet needs to know is the ipk and a rawnode leaf.

---

_[View the full topic](https://delvingbitcoin.org/t/tr-rawnode-and-rawleaf-support/901)._