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: <ArmchairCryptologist@protonmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 555A0C002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 9 Nov 2022 13:19:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 31D1E402F7
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 9 Nov 2022 13:19:36 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 31D1E402F7
Authentication-Results: smtp2.osuosl.org;
dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com
header.a=rsa-sha256 header.s=protonmail3 header.b=anhk+J+F
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level:
X-Spam-Status: No, score=-2.102 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, FREEMAIL_FROM=0.001,
RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-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 77UF5HQRePjL
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 9 Nov 2022 13:19:35 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org CCCE4402E5
Received: from mail-4322.protonmail.ch (mail-4322.protonmail.ch [185.70.43.22])
by smtp2.osuosl.org (Postfix) with ESMTPS id CCCE4402E5
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 9 Nov 2022 13:19:34 +0000 (UTC)
Date: Wed, 09 Nov 2022 13:19:28 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail3; t=1667999972; x=1668259172;
bh=U1sXsg5KtcduXEPiY7wHtYJSA4PC2+oaHyhigG+SKE8=;
h=Date:To:From:Subject:Message-ID:In-Reply-To:References:
Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
Message-ID:BIMI-Selector;
b=anhk+J+FseiAf+lenoMOTycz7R4cczuKsqzFQV+/dP9qh9yBeJOyEkRGqNrfAPOaZ
Ygqe9EjHds20dhjdY4tOCWLcoc9amhRZp+bfZ2yVFGnl4CXNrf2hUPlBpCS5VrM92m
0+l9pRnPby/2L2p0zFMCb/UhZxCaqi5K1CcPe29NO2wAhgnmJ/l9pNLnQpWtirFs60
+Kod3vjiVBPIotJ7s3p9MZjzB3uXCfkfuQtvUwCX0cNkiwFYC4INv/LAos6OBdjPbz
H8bYGcw0y2ZYad+l7K10a3jXjazgxJ74ldm2mgLEnr2bdAew8IUPXnh8iwsFnHJciZ
58MLgLinocuUg==
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: ArmchairCryptologist <ArmchairCryptologist@protonmail.com>
Message-ID: <fU-5B7MRAtu7RmJRfYnY0Jkv3d64dRyZDWCbpYJtqIoqhqrjuKDfWue2ddU8-O6JyUv2NL5iP_cpwNO-9e8s1WVepJAaCJa1IMMK6DXAWeA=@protonmail.com>
In-Reply-To: <Y05PHYtrNmA0vg7U@erisian.com.au>
References: <Y0ZTtlRSBihNN9+v@erisian.com.au>
<0hpdGx-1WbZdG31xaMXGHKTCjJ2-0eB5aIXUdsp3bqI1MlCx6TMZWROwpl1TVI5irrBqRN2-ydM6hmf3M5L-7ZQfazbx66oameiWTHayr6w=@wuille.net>
<Y0d/e2sEoNRgD7KP@erisian.com.au> <Y0u8Ee2Ao375z8UD@erisian.com.au>
<CALZpt+GSYBFxajSyZS19sQi4_6zHjkA5sP00V-pR=_NEVVUnkg@mail.gmail.com>
<Y05PHYtrNmA0vg7U@erisian.com.au>
Feedback-ID: 24244585:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 09 Nov 2022 13:23:00 +0000
Subject: Re: [bitcoin-dev] [Opt-in full-RBF] Zero-conf apps in immediate
danger
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: Wed, 09 Nov 2022 13:19:36 -0000
------- Original Message -------
On Tuesday, October 18th, 2022 at 9:00 AM, Anthony Towns via bitcoin-dev <b=
itcoin-dev@lists.linuxfoundation.org> wrote:
> I mean, if you think the feedback is wrong, that's different: maybe we
> shouldn't care that zeroconf apps are in immediate danger, and maybe
> bitcoin would be better if any that don't adapt immediately all die
> horribly as a lesson to others not to make similarly bad assumptions.
I've been following this discussion, and I wonder if there isn't a third so=
lution outside of "leave lightning vulnerable to pinning by non-RBF transla=
tions" and "kill zeroconf by introducing full-RBF" - specifically, adding a=
form of simple recursive covenant that "all descendant transactions of thi=
s transaction must use opt-in RBF for x blocks after this transaction is mi=
ned". This could be introduced either as a relay/mempool policy like RBF, o=
r in a full-fledged softfork.
Based on my admittedly not all-encompassing understanding of the bitcoin tr=
ansaction format, there are several unused bits in nSequence, which is alre=
ady used to flag RBF, that might be repurposed to flag the duration of this=
lock. Say if two bits were used for this, that would be enough to flag tha=
t the restriction is not used, or active for 100, 1000 and 10000 blocks.
I'm sure there may be other and potentially better ways of enabling this ty=
pe of covenant, but I'll leave that to the people who actually live and bre=
athe the bitcoin transaction format.
--
Regards,
ArmchairCryptologist
|
