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
|
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 6504FC000B
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Mar 2022 08:42:23 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id 4A827415AD
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Mar 2022 08:42:23 +0000 (UTC)
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
Authentication-Results: smtp4.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=protonmail.com
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 M2DuOPQZdpQW
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Mar 2022 08:42:22 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from mail-40135.protonmail.ch (mail-40135.protonmail.ch
[185.70.40.135])
by smtp4.osuosl.org (Postfix) with ESMTPS id 8D9054109F
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Mar 2022 08:42:22 +0000 (UTC)
Date: Fri, 04 Mar 2022 08:42:12 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail3; t=1646383339;
bh=Wgi2JgZ5KB/xX/f5oq0IqQ5wD2EhYirsqI3yPB+Qdng=;
h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To:
References:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
Message-ID;
b=UgzUj/0mmKnrdWGh69/vbBMmZbX8MZBrxqZTu/LwelB5NmJPdVh97JzKp1WayZEfW
Dz3xG/skfn03tAjr5RqeLltt3B+9kLxs6+6FE13R9UM1Vw3MzTYreQJdJNukhU2gKJ
SVgNBy/qqc9o+qIwsBPgNqPT/YuP/bIxjFJJ9CAeGYQ0o/e8AOBZx7l88SdJnaVwvv
JHBlME/8xo10dTHvf7EedaHOakPmbO2Z++6Vv5yw4wClOIarg55bTcHKKQdIs4hfmF
QzFRgd8+pEajPMyKN5gYirgbnyvoq08gUh3yPIFxBbCG7xmdb43XfG75JE6Nu957V2
ci9pNsWuAcXFA==
To: "vjudeu@gazeta.pl" <vjudeu@gazeta.pl>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <HLa5I3wJJu9SEQ2UD69HYFY1pwaIzvK1iQzdTggBVZkLHEdaXcp1UbLFiSMJOxcSZqr-EKYb7Irtxa7kI830XJamCqSy4jJ8WynGPqZ-xoM=@protonmail.com>
In-Reply-To: <132721155-8dab92d416edaf63c15cd32201400ae3@pmq8v.m5r2.onet>
References: <132721155-8dab92d416edaf63c15cd32201400ae3@pmq8v.m5r2.onet>
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] Recursive covenant opposition,
or the absence thereof,
was Re: TXHASH + CHECKSIGFROMSTACKVERIFY in lieu of CTV and
ANYPREVOUT
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: Fri, 04 Mar 2022 08:42:23 -0000
Good morning vjudeu,
> > Continuous operation of the sidechain then implies a constant stream of=
32-byte commitments, whereas continuous operation of a channel factory, in=
the absence of membership set changes, has 0 bytes per block being publish=
ed.
>
> The sidechain can push zero bytes on-chain, just by placing a sidechain h=
ash in OP_RETURN inside TapScript. Then, every sidechain node can check tha=
t "this sidechain hash is connected with this Taproot address", without pus=
hing 32 bytes on-chain.
The Taproot address itself has to take up 32 bytes onchain, so this saves n=
othing.
Regards,
ZmnSCPxj
|
