Ryan Grant [ARCHIVE] on Nostr: 📅 Original date posted:2022-08-10 📝 Original message:>> TODO: A way for the ...
📅 Original date posted:2022-08-10
📝 Original message:>> TODO: A way for the initial signer to delegate to another
>> scriptPubKey; needed for better privacy and CoinJoin/Lightning
>> compatibility
I need more documentation to understand this motivation.
On Tue, Aug 9, 2022 at 8:46 PM Ali Sherief via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> In the case of the last TODO, related to delegation to another
> scriptPubKey, I am not quite sure at the moment what to do about
> it - perhaps you guys can place a MAST (two Merkle branches, to be
> specific) - the first branch has the original signer's scriptPubKey,
> the second branch contains the delegated signer's scriptPubKey.
I don't understand this requirement, but it seems that whatever
parties are involved can make signatures on the delegating and
delegated keys.
📝 Original message:>> TODO: A way for the initial signer to delegate to another
>> scriptPubKey; needed for better privacy and CoinJoin/Lightning
>> compatibility
I need more documentation to understand this motivation.
On Tue, Aug 9, 2022 at 8:46 PM Ali Sherief via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> In the case of the last TODO, related to delegation to another
> scriptPubKey, I am not quite sure at the moment what to do about
> it - perhaps you guys can place a MAST (two Merkle branches, to be
> specific) - the first branch has the original signer's scriptPubKey,
> the second branch contains the delegated signer's scriptPubKey.
I don't understand this requirement, but it seems that whatever
parties are involved can make signatures on the delegating and
delegated keys.