summaryrefslogtreecommitdiff
path: root/ee/164b0bcfe395f64ca30d69bfcbc32b90fdcfa1
blob: f82ab615f453e3e460ce0c1074751edcfa6f0b81 (plain)
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
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
Return-Path: <pete@petertodd.org>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 3D840C002B
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 22 Feb 2023 16:39:13 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 0CDB6416ED
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 22 Feb 2023 16:39:13 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 0CDB6416ED
Authentication-Results: smtp2.osuosl.org; dkim=pass (2048-bit key,
 unprotected) header.d=messagingengine.com header.i=@messagingengine.com
 header.a=rsa-sha256 header.s=fm1 header.b=hFNoHTMU
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.603
X-Spam-Level: 
X-Spam-Status: No, score=-2.603 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 RCVD_IN_DNSWL_LOW=-0.7, 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 zJswPtMFFuaS
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 22 Feb 2023 16:39:12 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 100C7416CB
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com
 [64.147.123.24])
 by smtp2.osuosl.org (Postfix) with ESMTPS id 100C7416CB
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 22 Feb 2023 16:39:11 +0000 (UTC)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45])
 by mailout.west.internal (Postfix) with ESMTP id E24173200708;
 Wed, 22 Feb 2023 11:39:10 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162])
 by compute5.internal (MEProxy); Wed, 22 Feb 2023 11:39:11 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:cc:content-type:date:date:feedback-id
 :feedback-id:from:from:in-reply-to:in-reply-to:message-id
 :mime-version:references:reply-to:sender:subject:subject:to:to
 :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=
 fm1; t=1677083950; x=1677170350; bh=+pGk+7NSjRm/QTjrrme6YlTXFvQz
 NArE4UR0QdpBkB8=; b=hFNoHTMUKVbDeUrubTB5vOAZq/4k9dZatqE8puuGHvwA
 0IRy27YOYjr3liJnOruVvm0E3JRMIB3SnPt0XvDXLGtoSKC7N1U244M0XSJQz4/N
 LanpI0bOsJDQkySpkHUvQZRIzusxN3N/b6PXRzeR+afg9tMQ5gBKgqnzRbzkp/1I
 6j/Bkveu9eWrH9G+6svSWFXau29jFhywoAn22+GKEw9rt03sjSvBbdcL3uSdm7np
 gNtE7gXRgcdB6xlYKVD+9LYUVF6wR15lcapeglUwnpBm1OvA5xUEW0bB4qmGKnB0
 V+wQFxVfsCw/NG9At4d9RDwp1wTfZxzoeoCikYv6aA==
X-ME-Sender: <xms:LUX2Y2oxhk6_rQIotpju8TsmSjc-rEWEmKwRTAmk-8wz8HC7xfd03Q>
 <xme:LUX2Y0piNsF6d8_FgVH7FQyYFWVBB9GXiwrj4Zj86paUiIdgVAhXgzd-aQoIXZsg0
 lMzDETZkQ49Jw8T_qU>
X-ME-Received: <xmr:LUX2Y7OtDuB9InPwqketHtyp9usESUIqCAdzufff_Upx9Ww7UEAo0JgNLA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudejledgkeelucetufdoteggodetrfdotf
 fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
 uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne
 cujfgurhepfffhvfevuffkfhggtggujgesghdtreertddtvdenucfhrhhomheprfgvthgv
 rhcuvfhougguuceophgvthgvsehpvghtvghrthhouggurdhorhhgqeenucggtffrrghtth
 gvrhhnpeelvdellefftddukeduffejgfefjeeuheeileeftdfgteduteeggeevueethfej
 tdenucffohhmrghinhepphgvthgvrhhtohguugdrohhrghenucevlhhushhtvghrufhiii
 gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvgesphgvthgvrhhtohguugdr
 ohhrgh
X-ME-Proxy: <xmx:LkX2Y14zNjbKvMi9WRvjks9cZ5mqI5DWx_st0RHamE741JhxZVhlww>
 <xmx:LkX2Y14XJuIo8kc5nS-jbs2080aFzDBD0kQcKRaXsYFnaYpFP5O6kg>
 <xmx:LkX2Y1gDxRI0iVuUHPbtsgXIqDVzYcJ_50yxIv0MMka-cq0DvsWoxg>
 <xmx:LkX2Y40eG88GZEbvA4cT26-l4BaraVADGYV669eSVz1reFofJUSIng>
Feedback-ID: i525146e8:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed,
 22 Feb 2023 11:39:09 -0500 (EST)
Received: by localhost (Postfix, from userid 1000)
 id AFB865F92A; Wed, 22 Feb 2023 11:39:04 -0500 (EST)
Date: Wed, 22 Feb 2023 11:39:04 -0500
From: Peter Todd <pete@petertodd.org>
To: Andrew Poelstra <apoelstra@wpsoftware.net>
Message-ID: <Y/ZFKM2PGG+ijoBO@petertodd.org>
References: <TG0yVn41L6VFOHFRYqd3iGz7mxHWtjFdaBrz8mlP6Uk8bmog_isDbtq_2QyvdUs9_Q-jStmx7V7l5rAesXDfHlK9Ehft7SkK5EWQ_3mg-eQ=@protonmail.com>
 <177016307-23dca06637e70217317077657442d0d8@pmq7v.m5r2.onet>
 <Y/APRs3IPYapIpGg@camus>
 <B837E586-894E-40E8-9814-385EF59402B6@petertodd.org>
 <Y/Apxhqij1v56dT8@camus>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="eA6+M1CF4SFN2plB"
Content-Disposition: inline
In-Reply-To: <Y/Apxhqij1v56dT8@camus>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Testing censorship resistance of bitcoin p2p
 network
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, 22 Feb 2023 16:39:13 -0000


--eA6+M1CF4SFN2plB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 18, 2023 at 01:28:38AM +0000, Andrew Poelstra wrote:
> On Sat, Feb 18, 2023 at 02:03:15AM +0200, Peter Todd wrote:
> > On February 18, 2023 1:35:34 AM GMT+02:00, Andrew Poelstra via bitcoin-=
dev=20
> > >You could try statically analyze `<anything>` to determine whether the
> > >IF branch could ever be taken. For example there is no path through
> > >the "inscription script" that would result in all the crap being dropp=
ed
> > >by the end of the script, violating the CLEANSTACK rule.
> > >
> > >This sort of filtering, assuming it could be reliably and efficiently
> > >done, would at least force inscription scripts to be "plausible", and
> > >would greatly increase their space cost by e.g. requiring OP_DROP to be
> > >added somewhere hundreds of times.
> >=20
> > "greatly increase their space cost"?
> >=20
> > Tell me, what is the actual % increase to adding OP_DROPs like you prop=
ose?
> >
>=20
> By standardness rules (where you can have up to 80-byte pushes), a
> little over 1%. By consensus (520-byte pushes) less than 0.2%.
>=20
> Perhaps "greatly increase" is a stretch :) but if the fee market is
> functioning and we're talking about large amounts of data, it's not
> trivial either.

I would definitely call ~1% trivial. Fees vary more by that on an hour to h=
our
basis.

Anyway, it goes to show that protocols relying on data embedded in Bitcoin
transactions would do well to have flexible encoding rules, eg by consideri=
ng
all PUSHDATA's with certain characteristics to be data, so that encoders ca=
n be
adapted on the fly if there are any censorship issues. It's also useful if =
the
rules allow data to be encoded in UTXO outputs, so that censorship of witne=
ss
data always risks people switching to filling up the UTXO set. A kind of
Mutually Assured Destruction threat in a way.

FWIW, OpenTimestamps was deliberately designed to have this property. So do=
n't
mess with it. :D

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--eA6+M1CF4SFN2plB
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmP2RSYACgkQLly11TVR
Lzc5dw//VDyg9Dy7IzuB80yv9LXSoHR5Zv5sTlCYuUMUdhoanoYflKdMIiF8peGu
cJ7C7Xwx8+QIkNTUP+mgvlcTEETbZiC7F+k1n6eTavrYGpBMotVlkQHann+NxOU0
RPC2s17mc91Wo12tpbrp+vur4lQ3apnylDxeIeo0xkbsMzsX5XXGh0BPoD8aPT4y
jHo4TCBBIpXBOPI86VcbZKCgNrB2pZHRra3RHVjKFT9tyLM58A2qrtybMS2CzAj0
SmJAIzP1V1lmJSc6N/zlNuGwM6rBvG7o9UGZRENPq21Y0mPZ5YwlyerVnoE3AX21
Pwg7vMLOAd90VPmf/WjmGZx9x5050/AP3VmWTYsLnJDlmg/pPYtBF+SQ/EqJTsve
lfKSz23S5BFZnrG/6Vn5Vl7HKUfxuNT8/4tQbvZWlzWdX4o80zS3evrJ0Veb8Tv8
g4cPLUA5GGpwu5cm04LCDGyKMy5upX6rK9PiL3dRkuf3BZKfEpe9elLJxX5G2tSb
j3KvQFYOLRF0ycv4ecEdhMh6neKhCY4WqcuQGWcFGYg/yySrqA7UtXQfRjuEv8mJ
iGHGUNRO4Kz27Om7xDCy4gbi/Y3jBrK6twHcXK7Xid1EWIKFCkh6RWS8DBIi0iqD
K61Th/A6qn5r2DbOpeph/n91XZqv4u37KXHtgNt7o18Ue1GtfEk=
=Su2o
-----END PGP SIGNATURE-----

--eA6+M1CF4SFN2plB--