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
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
Return-Path: <user@petertodd.org>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
by lists.linuxfoundation.org (Postfix) with ESMTP id 35004C0012;
Thu, 9 Dec 2021 12:56:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id 22E1541E2B;
Thu, 9 Dec 2021 12:56:31 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level:
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1,
RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001,
RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp4.osuosl.org (amavisd-new);
dkim=fail (2048-bit key) reason="fail (message has been altered)"
header.d=petertodd.org
Received: from smtp4.osuosl.org ([127.0.0.1])
by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id St5q2laNuZxD; Thu, 9 Dec 2021 12:56:30 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from outmail148100.authsmtp.co.uk (outmail148100.authsmtp.co.uk
[62.13.148.100])
by smtp4.osuosl.org (Postfix) with ESMTPS id 9A44441E28;
Thu, 9 Dec 2021 12:56:29 +0000 (UTC)
Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237])
by punt17.authsmtp.com. (8.15.2/8.15.2) with ESMTP id 1B9CuQ0Z001935;
Thu, 9 Dec 2021 12:56:26 GMT (envelope-from user@petertodd.org)
Received: from petertodd.org (76-10-157-59.dsl.teksavvy.com [76.10.157.59])
(authenticated bits=0)
by mail.authsmtp.com (8.15.2/8.15.2) with ESMTPSA id 1B9CuOUD084574
(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
Thu, 9 Dec 2021 12:56:25 GMT (envelope-from user@petertodd.org)
Received: by petertodd.org (Postfix) with ESMTPSA id 337089E659;
Thu, 9 Dec 2021 07:56:23 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=petertodd.org; s=mail;
t=1639054583; bh=yoOeEhhhD3Zuu+nOw0RH016fZyuKY5sB4viL63WlAhM=;
h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
b=g974EOfyqIABMSxEiySRJgId4pgtJa77a0CSfF1I8mlwvXzPhZwYQt1Lm296lT0sg
pqckgl0yFo9+3oUcGS3GmzixmFV8IxVucpTGQwFTB6M53x8+qqpQY69QeNnyXGRU+N
YMqYAp8r2f7Ue+7RxwFZnPlyI0rL8kbA7tVim3SnAqLqgfiB45cKZM1txIJq/f/Fbx
MsXP3Pn7P00/Ok+92XhnhniXbIQUID9hW/+Idr/8cSrT0hfo+fkFJlT3VAaLggRJZA
m9zgAYTABXxx3gbDYAZ0YwB7sz6KZXHhTEANjDUXEp8/twQCpg+UBl4N7OIGvMquqA
8cOThgVPICkbg==
Received: by localhost (Postfix, from userid 1000)
id 44D355FB50; Thu, 9 Dec 2021 07:56:19 -0500 (EST)
Date: Thu, 9 Dec 2021 07:56:19 -0500
From: Peter Todd <pete@petertodd.org>
To: Alex Schoof <alex.schoof@gmail.com>
Message-ID: <YbH884j/+rZNcMjG@petertodd.org>
References: <DD7D5A8B-F61F-4302-ACF4-CE731843D97D@gmail.com>
<CALL-=e5mF9TqbbD=Cf-bawbw4dq2PGjC9W_nqAQeHsB829ZpNg@mail.gmail.com>
<CALkkCJas_pf7Un45CJyFg8j9cBk8PtKN4iYAL81TtLSRNnKqeg@mail.gmail.com>
<CANQKmgLyaYAjL_=LziTCFT=Ahc2SXjJrWc+RO59pxd3mnJApfQ@mail.gmail.com>
<YbHImwix1z8BgAc2@petertodd.org>
<CANQKmg+D22GrLFDBAawop1uha3GG5F4TmixMajcTPQUdTF4-PQ@mail.gmail.com>
<YbHVaU19CFvOQ3MB@petertodd.org>
<CA+2b5C1bfHnNtz6jWRmzr-2Dz3DpyvE1Z_LFCsJgBpbP-bULYQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
protocol="application/pgp-signature"; boundary="pa2N1icXw6EwdAH2"
Content-Disposition: inline
In-Reply-To: <CA+2b5C1bfHnNtz6jWRmzr-2Dz3DpyvE1Z_LFCsJgBpbP-bULYQ@mail.gmail.com>
X-Server-Quench: 6b0ba906-58ef-11ec-ba2e-8434971169dc
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZIVwkA IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
bwdMdgsUHFAXAgsB AWcbWlZeVVt7W2Y7 bAxPbAVDY09JQQBj T0pMXVMcFXdhcll+
Y2oeWh13cAEIen12 bUMsWCJbDhVzdUBg R0YBQ3AHZDIzdTJO UhVFfwdXdApNfx5D
YwQsGhFYa3VsGiM3 HxM1PjY+eDlSNhEd cQsMMVkVQEBOEjMi clg5EDMjHEsKDwIL
GCYLFmMmOg4PM0x6 G1o9UlUZNX1aLgxR H11LASlWTwAI
X-Authentic-SMTP: 61633532353630.1024:7600
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 76.10.157.59/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
lightning-dev <lightning-dev@lists.linuxfoundation.org>,
=?iso-8859-1?Q?H=E9ctor_Jos=E9_C=E1rdenas?= Pacheco <hcarpach@gmail.com>
Subject: Re: [bitcoin-dev] [Lightning-dev] Sending OP_RETURN via Bitcoin
Lightning
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, 09 Dec 2021 12:56:31 -0000
--pa2N1icXw6EwdAH2
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Dec 09, 2021 at 07:12:45AM -0500, Alex Schoof wrote:
> The multisig scheme is interesting. From my understanding of Single Use
> Seals, since seal n commits to seal n+1, for the on-chain aggregation sea=
ls
> you would want to pick some common aggregation service provider ahead of
> time and if that provider disappears, you=E2=80=99re stuck and cant close=
the next
> seal. If instead you say =E2=80=9Cthis seal commits to three of the five =
of these
> next seals=E2=80=9D then you mitigate both availability and censorship ri=
sk. Am I
> getting that right?
Re: "some common aggregation service provider", you might be misunderstandi=
ng
the protocol: since seals are trustless with regard to validity, I can vali=
date
your seal, regardless of which aggregation service you use.
But other than that, I think we're on the same page!
A concrete example would be an exchange: they do a lot of transactions, so =
they
could choose to be their own aggregator, and wouldn't need any multisig at =
all
because they can trust themselves not to censor themselves. :) Meanwhile, o=
ne
of their customers might use 3-of-5 as you suggest, as they only do a few
transactions a month.
Interestingly, in some scenarios it might be worthwhile to both run your own
aggregator, and use multisig. Eg Alice could use a 2-of-3 with two third-pa=
rty
aggregators, and her own aggregation chain. If both third-parties are up, s=
he
does no on-chain transactions at all; if one third-party is down, she can u=
se
her own, and the remaining third-party. Thus she would only do an on-chain
transaction to defeat censorship/failure.
--=20
https://petertodd.org 'peter'[:-1]@petertodd.org
--pa2N1icXw6EwdAH2
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmGx/O4ACgkQLly11TVR
LzfWYRAAvEuQRZUD/i5zS7BjPV8Ln+8m93ZaNm/WBfGh5q46P8uUY0jCUHz8ytPo
OBXzBiS2N1jS8QlIITZLzO5bo3k1QY3q10YTzuy32o1jdSSNcjE9Wrvvs8F5y4Wx
E8Y8ox+Yxz0AHjKgiKbTl+GEWnTwJoQWDWfdYaPHOcDhkNe7bacD/AcXi6wyH/dV
/eDRMeWM3Hj4ofSqjFT6dQ4qNWxJkr7G5Y+mNFmSNKXbl+3wsQejHdydBOcNYkQh
e3xTJ0JksmO+3T0WEMoiGaH3s3Gjx185U5KhP4r16heaFDnLlepx6b8j6V7/8++Q
bDRiAMa22hu4+s5K3A8dxicOHGn7JxzGRKeX/e47iVaon8J3SM3HcnSDBEVhP4/c
HDfWtm3N1XT0kk4VVBpzY1S3SpqfagYfMEbkzlzG4uQZzbpq522YZb/gP7B8UsHj
7iymWZoAwgZDs97lum1BnryKynYL4Pte2uo2vlVQKAXhcxG6iA8yQj7urf7+oY07
pjhfolvHOPMSCPomo7W4nt1SywtVCasP0rs8K/IYu6WhpBRqRGvD2knXBYLbQIW/
77p3S60EOOB9ohr6K4WDTFV3TeLO+/Z75rZclnCNspJ6EXSYLZ/qNg5y4nSSzuYw
uLQdcgjhHdHnZJ9+aqUVUYxcbiy/vT2k9R6KtYaTmScIkOTuEaw=
=f75x
-----END PGP SIGNATURE-----
--pa2N1icXw6EwdAH2--
|