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
183
184
185
186
187
188
189
190
191
192
193
|
Return-Path: <keagan.mcclelland@gmail.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
by lists.linuxfoundation.org (Postfix) with ESMTP id 26E06C0037
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 Dec 2023 22:39:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id E301141C21
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 Dec 2023 22:39:51 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org E301141C21
Authentication-Results: smtp4.osuosl.org;
dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
header.a=rsa-sha256 header.s=20230601 header.b=KbT526RC
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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,
HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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 s6pWHU8Q9r9v
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 Dec 2023 22:39:50 +0000 (UTC)
Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com
[IPv6:2607:f8b0:4864:20::22b])
by smtp4.osuosl.org (Postfix) with ESMTPS id 302CD41C1B
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 Dec 2023 22:39:50 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 302CD41C1B
Received: by mail-oi1-x22b.google.com with SMTP id
5614622812f47-3bb732e7d78so4288545b6e.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 Dec 2023 14:39:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20230601; t=1703716789; x=1704321589;
darn=lists.linuxfoundation.org;
h=to:subject:message-id:date:from:in-reply-to:references:mime-version
:from:to:cc:subject:date:message-id:reply-to;
bh=36vj7ZTlPmlNLQYVCZGMMLozUDO1npcn4Ya+lLmFQpw=;
b=KbT526RC+QgQv3OFr+dzBPPzZc/hhzD/YSY93nsEt+Ba996NJNS3hEMiNFJOCO/Df3
RXUFTzLpEFJ6tzbSi+UJNer4WX+RePCkKw76tfgQ3xExjhktuLOe6vVmjVizw6t4m4aM
SPz2bzZBLgaF8B/RzbvalL3InpQ9uZnX4m48H9E/1Y6xxOUVbNpXr5Ay67HiuAmMF6rm
Ra++hpx++dHvcz7l7gJfJRha3LzOA+522//TeLc5YsO6Kz0gj0Md4jRcq17hWbI0IqTY
kcxR9+ItIxMMZygdb7U5zBMW7DzeSOY3Y4Y0Fh0JwO+Wly6T9wBlJfrGXuw4S0kFvDvP
jNgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1703716789; x=1704321589;
h=to:subject:message-id:date:from:in-reply-to:references:mime-version
:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
bh=36vj7ZTlPmlNLQYVCZGMMLozUDO1npcn4Ya+lLmFQpw=;
b=cajUue8/cRwMCtaXKPbFNoh1rw3+KxeWFWAf057V3nr+O6/v2gDD4e5yIBYXadcfBd
/n1jiPywO0jXPeGLiI6/UwKEmxuOaWzsXrrGEywzw9nYOJYXlVuWp1imEE1zioMkczm2
muE4Y1qpZOKgJQAikhCd5Qcae+S64CkRV5TMzob5bVETuVEY0+S3Q+k0Z826q5QfFx+R
EXj1ZgWi3TU5Lb0BybeXP8GH6yAI5fgJVCCLs4qfeGiiIorqSAVaJPhyzHySjUqUytoM
lBle+1GVndu2Qgrso5gatePk37zLWAO+f8Kce+mAisVnYpcWos84k25QW8K/cebn8fzd
IkFA==
X-Gm-Message-State: AOJu0YwrD7zOBEvDems8p7KhjNm3f1mTBBcDLX91/wGJWmCJ2+pHZSWf
1ECyYwN5gjiJKR+DMz8VPE7lpt44B12Es0gdisU=
X-Google-Smtp-Source: AGHT+IEszL3/8AQQbb6n/OyOd2TUXEuTt/DAwugQp0OO8RKIEKxEPID6Gf2Ilaal22z89RORDfJRHfwawKjKGw0SqEQ=
X-Received: by 2002:a05:6808:2c2:b0:3bb:c658:594a with SMTP id
a2-20020a05680802c200b003bbc658594amr1208690oid.41.1703716789046; Wed, 27 Dec
2023 14:39:49 -0800 (PST)
MIME-Version: 1.0
References: <CAMHHROxsKuqzVsU90srQBNDj4redB11uqB2JxmDK=G1LDw9_HA@mail.gmail.com>
In-Reply-To: <CAMHHROxsKuqzVsU90srQBNDj4redB11uqB2JxmDK=G1LDw9_HA@mail.gmail.com>
From: Keagan McClelland <keagan.mcclelland@gmail.com>
Date: Wed, 27 Dec 2023 15:39:38 -0700
Message-ID: <CALeFGL2AZfVqchy=GWTDyehKXJkjYtCaonYFigv7ctHUnsxPfg@mail.gmail.com>
To: Greg Tonoski <gregtonoski@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000000250f4060d857a63"
X-Mailman-Approved-At: Thu, 28 Dec 2023 10:46:17 +0000
Subject: Re: [bitcoin-dev] [BUG]: Bitcoin blockspace price discrimination
put simple transactions at disadvantage
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, 27 Dec 2023 22:39:52 -0000
--0000000000000250f4060d857a63
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
> As a result, there are incentives structure distorted and critical
inefficiencies/vulnerabilities (e.g. misallocation of block space,
blockspace value destruction, disincentivized simple transaction,
centralization around complex transactions originators).
Can you please describe the mechanism here?
> Price of blockspace should be the same for any data (1 byte =3D 1 byte,
irrespectively of location inside or outside of witness), e.g. 205/205
and 767/767 bytes in the examples above.
"Should" ... to what end?
Keags
On Wed, Dec 27, 2023 at 10:26=E2=80=AFAM Greg Tonoski via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Blockspace price for data of a simple transaction is higher than the
> one for data of other ("complex") transactions: 3 vs 1.49
> "weight"/byte in the examples below:
> - 3=3D616 "weight" / 205 bytes (txid:
> aabbcce67f2aa71932f789cac5468d39e3d2224d8bebb7ca2c3bf8c41d567cdd)
> - 1.49=3D1140 "weight" / 767 bytes (txid:
> 1c35521798dde4d1621e9aa5a3bacac03100fca40b6fb99be546ec50c1bcbd4a).
>
> As a result, there are incentives structure distorted and critical
> inefficiencies/vulnerabilities (e.g. misallocation of block space,
> blockspace value destruction, disincentivized simple transaction,
> centralization around complex transactions originators).
>
> Price of blockspace should be the same for any data (1 byte =3D 1 byte,
> irrespectively of location inside or outside of witness), e.g. 205/205
> and 767/767 bytes in the examples above.
>
> Perhaps, the solution (the same price, "weight" of each bit of a
> transaction) could be introduced as part of the next version of Segwit
> transactions.
>
> Let's fix it. What do you think?
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--0000000000000250f4060d857a63
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">> As a result, there are incentives structure distorted=
and critical<br>inefficiencies/vulnerabilities (e.g. misallocation of bloc=
k space,<br>blockspace value destruction, disincentivized simple transactio=
n,<br>centralization around complex transactions originators).<br><br>Can y=
ou please describe the mechanism here?<div><br></div><div>> Price of blo=
ckspace should be the same for any data (1 byte =3D 1 byte,</div>irrespecti=
vely of location inside or outside of witness), e.g. 205/205<br>and 767/767=
bytes in the examples above.<br><div><br></div><div>"Should" ...=
to what end?</div><div><br></div><div>Keags</div></div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Dec 27, 2023 at 1=
0:26=E2=80=AFAM Greg Tonoski via bitcoin-dev <<a href=3D"mailto:bitcoin-=
dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>>=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Blocksp=
ace price for data of a simple transaction is higher than the<br>
one for data of other ("complex") transactions: 3 vs 1.49<br>
"weight"/byte in the examples below:<br>
- 3=3D616 "weight" / 205 bytes (txid:<br>
aabbcce67f2aa71932f789cac5468d39e3d2224d8bebb7ca2c3bf8c41d567cdd)<br>
- 1.49=3D1140 "weight" / 767 bytes (txid:<br>
1c35521798dde4d1621e9aa5a3bacac03100fca40b6fb99be546ec50c1bcbd4a).<br>
<br>
As a result, there are incentives structure distorted and critical<br>
inefficiencies/vulnerabilities (e.g. misallocation of block space,<br>
blockspace value destruction, disincentivized simple transaction,<br>
centralization around complex transactions originators).<br>
<br>
Price of blockspace should be the same for any data (1 byte =3D 1 byte,<br>
irrespectively of location inside or outside of witness), e.g. 205/205<br>
and 767/767 bytes in the examples above.<br>
<br>
Perhaps, the solution (the same price, "weight" of each bit of a<=
br>
transaction) could be introduced as part of the next version of Segwit<br>
transactions.<br>
<br>
Let's fix it. What do you think?<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--0000000000000250f4060d857a63--
|
