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
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
|
Return-Path: <vjudeu@gazeta.pl>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 2A291C0DCE
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 20 Nov 2023 19:47:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 01FD040A42
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 20 Nov 2023 19:47:26 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 01FD040A42
Authentication-Results: smtp2.osuosl.org;
dkim=pass (1024-bit key) header.d=gazeta.pl header.i=@gazeta.pl
header.a=rsa-sha256 header.s=2013 header.b=bZsA6ck1
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.604
X-Spam-Level:
X-Spam-Status: No, score=0.604 tagged_above=-999 required=5
tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001,
RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id e-cgA7XHg-R5
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 20 Nov 2023 19:47:23 +0000 (UTC)
Received: from smtpa34.poczta.onet.pl (smtpa34.poczta.onet.pl [213.180.142.34])
by smtp2.osuosl.org (Postfix) with ESMTPS id 3F0B140930
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 20 Nov 2023 19:47:22 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 3F0B140930
Received: from pmq1v.m5r2.onet (pmq1v.m5r2.onet [10.174.32.67])
by smtp.poczta.onet.pl (Onet) with ESMTP id 4SYyhM1Bjtz1BCT;
Mon, 20 Nov 2023 20:47:15 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gazeta.pl; s=2013;
t=1700509635; bh=tFIZzycw+tFJAUWKxKd2ek7fjvTFqXoVWv5HJEY5Vgo=;
h=From:Cc:To:Date:Subject:From;
b=bZsA6ck1mhIxyhdMF9vOHcp49UjZ2Yhb6HZHq02AXTMXVuXWsqHAWrxevd4EkRNTD
J33/sqJPzeiuMPzxnTj6IoWszMUHuNRr65btOJO+Z4tVtrREcHA7ThatO0DDs7bUD+
oa+BQ9Q0GwmHMxyh/o+XyZ5FEOtgGyEvrcNhuOno=
Content-Type: multipart/alternative;
boundary="===============4943912933812360673=="
MIME-Version: 1.0
Received: from [5.173.240.149] by pmq1v.m5r2.onet via HTTP id ;
Mon, 20 Nov 2023 20:47:15 +0100
From: vjudeu@gazeta.pl
X-Priority: 3
To: Anthony Towns <aj@erisian.com.au>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Date: Mon, 20 Nov 2023 20:47:13 +0100
Message-Id: <196556244-f24094b55827d9a09fa29ca8aa04b163@pmq1v.m5r2.onet>
X-Mailer: onet.poczta
X-Onet-PMQ: <vjudeu@gazeta.pl>;5.173.240.149;PL;3
X-Mailman-Approved-At: Mon, 20 Nov 2023 19:51:58 +0000
Cc: Casey Rodarmor <casey@rodarmor.com>
Subject: Re: [bitcoin-dev] Purely off-chain coin colouring
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: Mon, 20 Nov 2023 19:47:26 -0000
This is a multi-part message in MIME format.
--===============4943912933812360673==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
> Sign-to-contract looks like:
=C2=A0
Nice! I think it should be standardized as some informational BIP. This is =
a similar case as with Silent Payments: it is possible to let users make th=
eir own commitments as they please, but if it will be officially standardiz=
ed, then it will be possible to build more protocols on top of that, in a w=
ay which will be understood properly by other nodes.
=C2=A0
Before, I thought about interpreting signature R-value just as a Taproot-ba=
sed public key, and forming a commitment as a valid input, that would allow=
moving coins on such address, but maybe we could standardize it in a simpl=
er way than that. In general, if a commitment would allow pushing any data,=
it could be always extended when needed, because future commitments could =
be always nested in the old ones, 32 bytes is enough to do that.
=C2=A0
Also, I thought about including OP_RETURN at the beginning of each commitme=
nt, to make sure it will be never pushed on-chain, but only stored and proc=
essed off-chain. Another thing is that r-value is always expressed as some =
256-bit number, even in DER encoding, which means we can always assume 02 p=
ublic key prefix in all commitments, and simply convert it directly into a =
proper Taproot address.
--===============4943912933812360673==
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
<div>
<div>> Sign-to-contract looks like:</div>
<div> </div>
<div>Nice! I think it should be standardized as some informational BIP. Thi=
s is a similar case as with Silent Payments: it is possible to let users ma=
ke their own commitments as they please, but if it will be officially stand=
ardized, then it will be possible to build more protocols on top of that, i=
n a way which will be understood properly by other nodes.</div>
<div> </div>
<div>Before, I thought about interpreting signature R-value just as a Tapro=
ot-based public key, and forming a commitment as a valid input, that would =
allow moving coins on such address, but maybe we could standardize it in a =
simpler way than that. In general, if a commitment would allow pushing any =
data, it could be always extended when needed, because future commitments c=
ould be always nested in the old ones, 32 bytes is enough to do that.</div>
<div> </div>
<div>Also, I thought about including OP_RETURN at the beginning of each com=
mitment, to make sure it will be never pushed on-chain, but only stored and=
processed off-chain. Another thing is that r-value is always expressed as =
some 256-bit number, even in DER encoding, which means we can always assume=
02 public key prefix in all commitments, and simply convert it directly in=
to a proper Taproot address.</div>
</div>
--===============4943912933812360673==--
|
