From: Ryan Grant <bitcoin-dev@rgrant.org>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Cc: Ali Sherief <ali@notatether.com>
Subject: Re: [bitcoin-dev] Regarding BIP322 edge cases
Date: Wed, 10 Aug 2022 23:11:10 +0000 [thread overview]
Message-ID: <CAMnpzfpy=jpf+VncX6jUZnWEJV1dgwpQRSxzydMHoXoOZfRdbA@mail.gmail.com> (raw)
In-Reply-To: <20220809130908.yykum37tre7um4j3@artanis>
>> 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@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.
next prev parent reply other threads:[~2022-08-10 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 13:09 [bitcoin-dev] Regarding BIP322 edge cases Ali Sherief
2022-08-10 2:59 ` vjudeu
2022-08-10 23:11 ` Ryan Grant [this message]
2022-08-11 16:56 ` Ali Sherief
[not found] <mailman.5.1660132803.3395.bitcoin-dev@lists.linuxfoundation.org>
2022-08-10 13:53 ` Ali Sherief
2022-08-10 15:05 vjudeu
2022-08-10 16:42 ` Ali Sherief
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMnpzfpy=jpf+VncX6jUZnWEJV1dgwpQRSxzydMHoXoOZfRdbA@mail.gmail.com' \
--to=bitcoin-dev@rgrant.org \
--cc=ali@notatether.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox