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"
Subject: Re: [bitcoin-dev] [BUG]: Bitcoin blockspace price discrimination
 put simple transactions at disadvantage
Precedence: list

--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">&gt; 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>&gt; 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>&quot;Should&quot; ...=
 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 &lt;<a href=3D"mailto:bitcoin-=
dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt=
; 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 (&quot;complex&quot;) transactions: 3 vs 1.49<br>
&quot;weight&quot;/byte in the examples below:<br>
- 3=3D616 &quot;weight&quot; / 205 bytes (txid:<br>
aabbcce67f2aa71932f789cac5468d39e3d2224d8bebb7ca2c3bf8c41d567cdd)<br>
- 1.49=3D1140 &quot;weight&quot; / 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, &quot;weight&quot; of each bit of a<=
br>
transaction) could be introduced as part of the next version of Segwit<br>
transactions.<br>
<br>
Let&#39;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--