diff options
author | Andrew Chow <achow101-github@achow101.com> | 2022-08-09 16:26:17 -0400 |
---|---|---|
committer | Andrew Chow <achow101-github@achow101.com> | 2022-08-09 16:36:00 -0400 |
commit | ac59112a6a093e641ce2803260dd9de97b1cd961 (patch) | |
tree | 0d5e7e69bd3ac628195cfad542bb95c607160494 /src/outputtype.cpp | |
parent | c012875b9ded0a5183602f002738ca823d559518 (diff) | |
parent | 544b4332f0e122167bdb94dc963405422faa30cb (diff) | |
download | bitcoin-ac59112a6a093e641ce2803260dd9de97b1cd961.tar.xz |
Merge bitcoin/bitcoin#23480: Add rawtr() descriptor for P2TR with specified (tweaked) output key
544b4332f0e122167bdb94dc963405422faa30cb Add wallet tests for spending rawtr() (Pieter Wuille)
e1e3081200a71b6c9b0dcf236bc2a37ed1aa7552 If P2TR tweaked key is available, sign with it (Pieter Wuille)
8d9670ccb756592bddb2a269bf5078d62658537b Add rawtr() descriptor for P2TR with unknown tweak (Pieter Wuille)
Pull request description:
It may be useful to be able to represent P2TR outputs in descriptors whose script tree and/or internal key aren't known. This PR does that, by adding a `rawtr(KEY)` descriptor, where the KEY represents the output key directly. If the private key corresponding to that output key is known, it also permits signing with it.
I'm not convinced this is desirable, but presumably "tr(KEY)" sounds more intended for direct use than "rawtr(KEY)".
ACKs for top commit:
achow101:
ACK 544b4332f0e122167bdb94dc963405422faa30cb
sanket1729:
code review ACK 544b4332f0e122167bdb94dc963405422faa30cb
w0xlt:
reACK https://github.com/bitcoin/bitcoin/pull/23480/commits/544b4332f0e122167bdb94dc963405422faa30cb
Tree-SHA512: 0de08de517468bc22ab0c00db471ce33144f5dc211ebc2974c6ea95709f44e830532ec5cdb0128c572513d352120bd651c4559516d4500b5b0a3d257c4b45aca
Diffstat (limited to 'src/outputtype.cpp')
0 files changed, 0 insertions, 0 deletions