From: Keagan McClelland <keagan.mcclelland@gmail•com>
To: Greg Tonoski <gregtonoski@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] [BUG]: Bitcoin blockspace price discrimination put simple transactions at disadvantage
Date: Wed, 27 Dec 2023 15:39:38 -0700 [thread overview]
Message-ID: <CALeFGL2AZfVqchy=GWTDyehKXJkjYtCaonYFigv7ctHUnsxPfg@mail.gmail.com> (raw)
In-Reply-To: <CAMHHROxsKuqzVsU90srQBNDj4redB11uqB2JxmDK=G1LDw9_HA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]
> 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 = 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 AM 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=616 "weight" / 205 bytes (txid:
> aabbcce67f2aa71932f789cac5468d39e3d2224d8bebb7ca2c3bf8c41d567cdd)
> - 1.49=1140 "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 = 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
>
[-- Attachment #2: Type: text/html, Size: 2584 bytes --]
next prev parent reply other threads:[~2023-12-27 22:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 16:44 Greg Tonoski
2023-12-27 19:06 ` Nagaev Boris
2024-01-13 15:04 ` Greg Tonoski
2024-01-16 23:29 ` Nagaev Boris
2024-01-21 17:14 ` Greg Tonoski
2023-12-27 22:39 ` Keagan McClelland [this message]
2024-01-14 13:10 ` Greg Tonoski
2024-01-16 23:40 ` Nagaev Boris
2023-12-27 21:43 vjudeu
2024-01-16 10:40 ` Greg Tonoski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALeFGL2AZfVqchy=GWTDyehKXJkjYtCaonYFigv7ctHUnsxPfg@mail.gmail.com' \
--to=keagan.mcclelland@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gregtonoski@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox