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
|
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138])
by lists.linuxfoundation.org (Postfix) with ESMTP id 46625C002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 19 Sep 2022 22:43:56 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id 1A93B8141A
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 19 Sep 2022 22:43:56 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 1A93B8141A
Authentication-Results: smtp1.osuosl.org;
dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com
header.a=rsa-sha256 header.s=protonmail3 header.b=f0c+DUhn
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.298
X-Spam-Level:
X-Spam-Status: No, score=0.298 tagged_above=-999 required=5
tests=[BAYES_20=-0.001, 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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id G-CucjdlIeCg
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 19 Sep 2022 22:43:55 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org D2BF381410
Received: from mail-40140.protonmail.ch (mail-40140.protonmail.ch
[185.70.40.140])
by smtp1.osuosl.org (Postfix) with ESMTPS id D2BF381410
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 19 Sep 2022 22:43:54 +0000 (UTC)
Date: Mon, 19 Sep 2022 22:43:44 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail3; t=1663627432; x=1663886632;
bh=Kevp//Fawv/J7zdsa/rot5W639NKwIMW7baMBrsD5gQ=;
h=Date:To:From:Subject:Message-ID:In-Reply-To:References:
Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
Message-ID;
b=f0c+DUhn6wMMlynQ48lKnewuq3rzY6b3s5ieGCueV+uHo6DBo7mxp1r9FeT4JZ0ZB
5aSYZrvgye00sowb5xKlXooOVIzpapGihQn5CEQJHOTOhOLolx8XrHRkcUPAKjHpaH
za3losWWalEJrCET5JBdWyeXuQQ6BXL4yI9J1I6A5NyLWRy4tDp+plilpFJ19K3rqp
pFY6hGSuWnxHfqPHhlXoZGRnaWFTSiQyd596sGb6sO+5gpVI/VaA0Dcqjk/mP3bZmr
SQNVaAiB0Ub9NA7XkW3Wq4mYKICggrB1rBtzcQaIHi5RdwZurlSDcGG3fXGNcIbAfJ
s7sx0qpQAbIxA==
To: Jeremy Rubin <jeremy.l.rubin@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <iy7h2Ef6lbbHkutZVhZQZgPo9FPKIsGWJwAiO1CnSdj6ljY884qlURJDP3ifnPHxK169_FY1Vi48-3kvuNO-Ekt6gz4uNQv66BE4mUDuWOY=@protonmail.com>
In-Reply-To: <CAD5xwhgKGMx79+RLpb-hjd3Gc=EKxTVzkpME-=KuM_C5+d7mRQ@mail.gmail.com>
References: <CAD5xwhgKGMx79+RLpb-hjd3Gc=EKxTVzkpME-=KuM_C5+d7mRQ@mail.gmail.com>
Feedback-ID: 2872618:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [bitcoin-dev] Spookchains: Drivechain Analog with One-Time
Trusted Setup & APO
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, 19 Sep 2022 22:43:56 -0000
Good morning Jeremy,
Excellent work!
> # Terminal States / Thresholds
>=20
> When a counter reaches the Nth state, it represents a certain amount
> of accumulated work over a period where progress was agreed on for
> some outcome.
>=20
> There should be some viable state transition at this point.
>=20
> One solution would be to have the money at this point sent to an
> `OP_TRUE` output, which the miner incrementing that state is
> responsible for following the rules of the spookchain.
This is not quite Drivechain, as Drivechains precommit to the final state t=
ransition when the counter reaches threshold and mainchain-level rules prev=
ent the miner who does the final increment from "swerving the car" to a dif=
ferent output, whereas use of `OP_TRUE` would not prevent this; the Spookch=
ain could vote for one transition, and then the lucky last miner can output=
a different one, and only other miners interested in the sidechain would r=
eject them (whereas in the Drivechain case, even nodes that do not care abo=
ut the sidechain would reject).
Still, it does come awfully close, and the "ultimate threat" ("nuclear opti=
on") in Drivechains is always that everyone upgrades sidechain rules to mai=
nchain rules, which would still work for Spookchains.
Not sure how comfortable Drivechain proponents would be with this, though.
(But given the demonstrated difficulty in getting consensus changes for the=
blockchain, I wonder if this nuclear option is even a viable threat)
> Or, it could be
> specified to be some administrator key / federation for convenience,
> with a N block timeout that degrades it to fewer signers (eventually
> 0) if the federation is dead to allow recovery.
Seems similar to the Blockstream separation of the block-signing functionar=
ies from the money-keeping functionaries.
Regards,
ZmnSCPxj
|
