1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
|
Return-Path: <ali@notatether.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 244C8C002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 11 Aug 2022 16:56:43 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id 0896D60B6F
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 11 Aug 2022 16:56:41 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 0896D60B6F
Authentication-Results: smtp3.osuosl.org; dkim=pass (2048-bit key,
unprotected) header.d=notatether.com header.i=@notatether.com
header.a=rsa-sha256 header.s=protonmail header.b=h78LTvuk
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id s-8BOujn68AX
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 11 Aug 2022 16:56:40 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 2B1FC60B52
Received: from mail-40136.proton.ch (mail-40136.proton.ch [185.70.40.136])
by smtp3.osuosl.org (Postfix) with ESMTPS id 2B1FC60B52
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 11 Aug 2022 16:56:38 +0000 (UTC)
Date: Thu, 11 Aug 2022 16:56:29 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=notatether.com;
s=protonmail; t=1660236995; x=1660496195;
bh=9aVcpIYuaWI76G1gT80uVNGKzPbQvOhhtqefWj19Ah0=;
h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To:
References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To:
Feedback-ID:Message-ID;
b=h78LTvukDfYO47gc/J/dSvFu34bMHl22F1XyYDleLkEfjQ0oFWnvGPZcnAOgT24xx
Tjza0Mdq1wes11paBaPVZXfYCBGEBUk06hFx5rqf6orZ3NLQeSC2L9h0h3kshbrFON
XR/cw3OaVUI4OsicKmj550O/8bvH1ta2t2shaGhkJerFxesw/0WTk5KXr44HZmiU4O
Rku7Lwolqiv8qYzQzKco/rFkpHOscpxc3kXu6IRlKWqOz+6aFV+9TvqWBDgQqGtu6y
DLBEm+SnAOAQofQlVMndkicYqsiw6DC9ZEs4pEbMG8Fkfw2ALp3hrrwk+y6dAebCDn
kG1anGnTeUyTg==
To: Ryan Grant <bitcoin-dev@rgrant.org>
From: Ali Sherief <ali@notatether.com>
Reply-To: Ali Sherief <ali@notatether.com>
Message-ID: <20220811165622.etfdfiiawsdpljmy@artanis>
In-Reply-To: <CAMnpzfpy=jpf+VncX6jUZnWEJV1dgwpQRSxzydMHoXoOZfRdbA@mail.gmail.com>
References: <20220809130908.yykum37tre7um4j3@artanis>
<CAMnpzfpy=jpf+VncX6jUZnWEJV1dgwpQRSxzydMHoXoOZfRdbA@mail.gmail.com>
Feedback-ID: 34210769:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 11 Aug 2022 17:47:33 +0000
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Regarding BIP322 edge cases
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2022 16:56:43 -0000
Earlier last year on March, there was a post here by Jeremy Rubin that expl=
ains how a person could delegate its UTXO to some script, by (AFAICT) creat=
ing 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 mess=
age signing transactions too.
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018615.h=
tml
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.
|
