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
|
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
by lists.linuxfoundation.org (Postfix) with ESMTP id B8BC9C0032
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 7 Nov 2023 11:12:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id 9C10161392
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 7 Nov 2023 11:12:10 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 9C10161392
Authentication-Results: smtp3.osuosl.org;
dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com
header.a=rsa-sha256 header.s=protonmail3 header.b=J21y4ZJX
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.599
X-Spam-Level:
X-Spam-Status: No, score=-1.599 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,
FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_MSPIKE_H5=0.001,
RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-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 TPbi5a7-YzG4
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 7 Nov 2023 11:12:09 +0000 (UTC)
Received: from mail-40130.protonmail.ch (mail-40130.protonmail.ch
[185.70.40.130])
by smtp3.osuosl.org (Postfix) with ESMTPS id 45AA461388
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 7 Nov 2023 11:12:09 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 45AA461388
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail3; t=1699355527; x=1699614727;
bh=uig3cHZwy8EEt7LRCUj639oHg0eVzbK/UyhuICUci4g=;
h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References:
Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
Message-ID:BIMI-Selector;
b=J21y4ZJXNpkFKUx7izn39Zcq9gdI/8NDPmZa/oB+E9nJMFz/VNr7f3BeIc43/TLDQ
uJN6u6ChYhmWAkArP5jkChMJ2oBG/DITm/1bsJJHScFk6U5yRWKaKSkyaNnrC9+ZoN
CvRVs4jI51AS6M0HIyRd2xK0njTZhiQHcfwWwdjgXtXMGfPqXnfPTUVlqaVSGEAsMK
ON5FSa/LFK4hy6398p1wHUyWUVkA0COBW9hVcPeaEleGZS59pMygrg2VjANBo4NzDK
5BA/+UK0RFjqngPRgBWj26W/EsKzxXgh4nLn9k+7TG4GHJRrsgwK8GzK3j2ujkvx27
5bIiEA8SfAluw==
Date: Tue, 07 Nov 2023 11:11:59 +0000
To: Antoine Riard <antoine.riard@gmail.com>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <iBopsZOx5TRDjjfxSLo9GLa00c7Jk0uMSae6_EPsPjnd10Aa87-lxVIZnL37GwEM3ppemBAxCwkv7r4w5AfDjLkKo0OhIpdB0jK0_OTRqf4=@protonmail.com>
In-Reply-To: <CALZpt+GXGBbo0JjOyMr3B-3dVY2Q_DuzF6Sn3xE5W24x77PRYg@mail.gmail.com>
References: <CALZpt+GdyfDotdhrrVkjTALg5DbxJyiS8ruO2S7Ggmi9Ra5B9g@mail.gmail.com>
<ZTMWrJ6DjxtslJBn@petertodd.org>
<CALZpt+GQ9g-uwAGYogdaJcinVHRxs4=67hML78KbramJg=davA@mail.gmail.com>
<ZUNBHsw2BldPLvPc@petertodd.org>
<CALZpt+GBcqquPtf0YB07Rcy2OS0kUhv86s6g=69VrfSE72cYJQ@mail.gmail.com>
<ZUXyICh45JP6OnDu@petertodd.org>
<CALZpt+GXGBbo0JjOyMr3B-3dVY2Q_DuzF6Sn3xE5W24x77PRYg@mail.gmail.com>
Feedback-ID: 2872618:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
"lightning-dev\\\\\\\\@lists.linuxfoundation.org"
<lightning-dev@lists.linuxfoundation.org>, security@ariard.me
Subject: Re: [bitcoin-dev] [Lightning-dev] OP_Expire and Coinbase-Like
Behavior: Making HTLCs Safer by Letting Transactions Expire Safely
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: Tue, 07 Nov 2023 11:12:10 -0000
Good morning Antoine,
> Once the HTLC is committed on the Bob-Caroll link, Caroll releases the pr=
eimage off-chain to Bob with an `update_fulfill_htlc` message, though Bob d=
oes _not_ send back his signature for the updated channel state.
>=20
> Some blocks before 100, Caroll goes on-chain to claim the inbound HTLC ou=
tput with the preimage. Her commitment transaction propagation in network m=
empools is systematically "replaced cycled out" by Bob.
I think this is impossible?
In this scenario, there is an HTLC offered by Bob to Carol.
Prior to block 100, only Carol can actually create an HTLC-success transact=
ion.
Bob cannot propagate an HTLC-timeout transaction because the HTLC timelock =
says "wait till block 100".
Neither can Bob replace-recycle out the commitment transaction itself, beca=
use the commitment transaction is a single-input transaction, whose sole in=
put requires a signature from Bob and a signature from Carol --- obviously =
Carol will not cooperate on an attack on herself.
So as long as Carol is able to get the HTLC-success transaction confirmed b=
efore block 100, Bob cannot attack.
Of course, once block 100 is reached, `OP_EXPIRE` will then mean that Carol=
cannot claim the fund anymore.
Regards,
ZmnSCPxj
|
