Add bip-internalkey #1534
Add bip-internalkey #1534
Conversation
reardencode
force-pushed
the
internalkey
branch
from
4d448cc
to
a24aca4
Compare
bip-internalkey.mediawiki
Outdated
|
|
||
| When building taproot outputs, especially those secured by an aggregate key | ||
| representing more than 1 signer; the parties may wish to collaborate on signing | ||
| with the taproot internal key, but only with additional script restrictions. In |
There was a problem hiding this comment.
Can you give an example where using the key path with an aggregate key and having every participant enforce the additional restrictions themselves (i.e. only signing if they're met) wouldn't suffice?
There was a problem hiding this comment.
The most obvious case would be lightning symmetry where the parties want to pre-sign with CTV+CSFS to create a rebindable update transaction.
reardencode
force-pushed
the
internalkey
branch
2 times, most recently
from
c9842c4
to
729276c
Compare
|
Updated to match the BIN. |
jonatack
added
Needs number assignment
New BIP
and removed
Needs number assignment
labels
reardencode
force-pushed
the
internalkey
branch
2 times, most recently
from
34e2010
to
978f4cd
Compare
reardencode
force-pushed
the
internalkey
branch
from
978f4cd
to
efd4bd9
Compare
| | BIP-XXXX | `OP_INTERNALKEY` | ||
| | :--------- | :--------------- | ||
| | Layer | Consensus (soft fork) | ||
| | Author | Brandon Black `<freedom@reardencode.com>`, Jeremy Rubin `<j@rubin.io>` | ||
| | Discussion | https://delvingbitcoin.org/t/lnhance-bips-and-implementation/376/9 | ||
| | Status | Draft | ||
| | Type | Standards Track | ||
| | Created | 2023-12-22 | ||
| | License | BSD-3-Clause |
There was a problem hiding this comment.
Please use the preamble format specified in BIP2.
Instead of "BIP-XXXX" there should be a "BIP" header. The "Title" header is missing, the "Comments-URI" header is missing, and "Discussion" should be "Post-History".
murchandamus
added
the
PR Author action required
| [BIP 342]), `OP_INTERNALKEY` replaces `OP_SUCCESS203` (0xcb). `OP_INTERNALKEY` | ||
| pushes the taproot internal key, as defined in [BIP 341], to the stack. | ||
|
|
||
| ## Motivation |
There was a problem hiding this comment.
Additional useful feature: ability to inspect the tweak to a key (in combination with some OP_TWEAKVERIFY).
OP_INTERNALKEY is a new BIP342 tapscript only opcode (upgraded using OP_SUCCESS semantics) that takes bytes 1-32 (0-index, inclusive) from the BIP341 taproot control block and places them on the stack. This BIP describes that behavior.