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
|
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
by lists.linuxfoundation.org (Postfix) with ESMTP id 60EEFC0032
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 30 Aug 2023 11:05:25 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id 2E01241BEE
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 30 Aug 2023 11:05:25 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 2E01241BEE
Authentication-Results: smtp4.osuosl.org;
dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com
header.a=rsa-sha256 header.s=protonmail3 header.b=Yz0xKEwK
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 smtp4.osuosl.org ([127.0.0.1])
by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id cEfBoK2PebYw
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 30 Aug 2023 11:05:24 +0000 (UTC)
Received: from mail-4319.protonmail.ch (mail-4319.protonmail.ch [185.70.43.19])
by smtp4.osuosl.org (Postfix) with ESMTPS id CFB1C407D7
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 30 Aug 2023 11:05:23 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org CFB1C407D7
Date: Wed, 30 Aug 2023 11:05:03 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail3; t=1693393521; x=1693652721;
bh=FlGb2KUtxHpzsGuvdNh40edkYAtEamAp0J0Ye0EC3G0=;
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=Yz0xKEwKPoTcUlUDAeMtn3+94vmJ3qdXUJJF99e3AaA0RKUhdcKVqC3AdnVR50tQn
TihQq8iQi4dGCuEEM8nd9K/LbTEF45iRSuMri14ubimY+HDWyiACnbB47FAbJKmbXv
kC70+5J+Q41uZYgOSUra+xOvbWERL/Fj2OY/SmGkNN9rs5ly3J4nH6jSTk7hCxoZNx
5mYDSBAGttuStLnhALklcXVJm9rZ/28qAf9ixDGA3MeT2bFB4SZ1tmFHW4HeBY8omy
j2e6ZltSJTKwd1zQ0MDf4B2gRQgKAK19HtJ3SAj6o++dJh0IaRUKnYHVfjcRBzmqa9
cUDAMgmORgyGA==
To: ryan@breen.xyz
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <E9WH5C46HJT_uwLTnliTeZSZPrPwoKQs57muUxPVzaGWCWWriC4m2HGVoagR8dfvRBU_1qGtvlhojqIf_854em3_bJIR6DzAqAGHR6fW_nI=@protonmail.com>
In-Reply-To: <0D44C322-E2B4-4F80-A5D8-7D8304BDAE1A@breen.xyz>
References: <E4A37B75-349D-4CD8-B8E2-9686EFDA9EEA@breen.xyz>
<CAPv7TjZf4nLpCZPDOWK=vJGQuH0waTXkM6h40tc7G+YKAOGOGQ@mail.gmail.com>
<2BFA7EE8-2E0E-45A3-AC11-8E57F99EC775@breen.xyz>
<2FylpMx7IsZBt3ILxEt9pVB0Kq03jZqTUeLnB2hWT5j8qiB4o6plW3gjhBXQ_7p4MwQ_npQUpZ64hQaR6UnLhMNCnk_jCv1XObmrJbjrVqg=@protonmail.com>
<0D44C322-E2B4-4F80-A5D8-7D8304BDAE1A@breen.xyz>
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>
Subject: Re: [bitcoin-dev] Sentinel Chains: A Novel Two-Way Peg
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, 30 Aug 2023 11:05:25 -0000
Good morning Ryan,
> I appreciate your questions, ZmnSCPxj.
>=20
> I will answer your second question first: Mainchain nodes do not ever val=
idate sidechain blocks. Sidechain nodes watch Bitcoin for invalid withdrawa=
ls, and publish signed attestations to a public broadcast network (such as =
Nostr) that a transaction is making an invalid withdrawal. These sidechain =
nodes are the so-called sentinels.
Let me reiterate my question:
Suppose I trust some sidechain node that is publishing such an attestation.
Then the sidechain node is hacked or otherwise wishes to disrupt the networ=
k for its own purposes.
And it attests that a valid sidechain withdrawal is actually invalid.
What happens then?
To the point, suppose that the attestation private key is somehow leaked or=
determined by a third party that has incentive to disrupt the mainchain ne=
twork.
And it seems to me that this can be used to force some number of nodes to f=
ork themselves off the network.
This is dangerous as nodes may be monitoring the blockchain for time-sensit=
ive events, such as Lightning Network theft attempts.
Making "fork off bad miners!" a regular occurrence seems dangerous to me.
Regards,
ZmnSCPxj
|
