From: Ali Sherief <ali@notatether•com>
To: Ryan Grant <bitcoin-dev@rgrant•org>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Regarding BIP322 edge cases
Date: Thu, 11 Aug 2022 16:56:29 +0000 [thread overview]
Message-ID: <20220811165622.etfdfiiawsdpljmy@artanis> (raw)
In-Reply-To: <CAMnpzfpy=jpf+VncX6jUZnWEJV1dgwpQRSxzydMHoXoOZfRdbA@mail.gmail.com>
Earlier last year on March, there was a post here by Jeremy Rubin that explains how a person could delegate its UTXO to some script, by (AFAICT) creating a new transaction using that UTXO, with whatever script you want it to have.
It was written in terms of normal transactions, but can be extended to message signing transactions too.
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018615.html
Only the beginning of the post is relevant here.
- Ali
On Wed, Aug 10, 2022 at 11:11:10PM +0000, Ryan Grant wrote:
> >> 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-11 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 13:09 Ali Sherief
2022-08-10 2:59 ` vjudeu
2022-08-10 23:11 ` Ryan Grant
2022-08-11 16:56 ` Ali Sherief [this message]
[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=20220811165622.etfdfiiawsdpljmy@artanis \
--to=ali@notatether$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=bitcoin-dev@rgrant$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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