From: Greg Tonoski <gregtonoski@gmail•com>
To: Nagaev Boris <bnagaev@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] [BUG]: Bitcoin blockspace price discrimination put simple transactions at disadvantage
Date: Sun, 21 Jan 2024 18:14:14 +0100 [thread overview]
Message-ID: <CAMHHROzkqCVJQc7uszmtATiWWSm=WAEa2QmSxhcevCQowCyb9w@mail.gmail.com> (raw)
In-Reply-To: <CAFC_Vt4aDvWsUh4q+UxFa3ZyRC_eK2ek7HR-G+nOiaC-wSa-WA@mail.gmail.com>
On Wed, Jan 17, 2024 at 12:30 AM Nagaev Boris <bnagaev@gmail•com> wrote:
>
> Node operators are likely to put UTXO set to SSD and blocks to HDD.
> SSD is more expensive than HDD.
Again, the UTXO set size argument is irrelevant. A simple transaction
is at disadvantage even if it doesn't result in a change of UTXO set
size.
> It is aligned with the fact that
> people putting data into blockchain are financially motivated to put
> it into witness data, i.e. into HDD. If miners charge the same per 1
> byte in a transaction output and 1 byte in witness, then people
> putting data into blockchain could put it into transaction outputs
> (why not, if the price is the same), (...)
By the same token, "people putting data into blockchain are
financially" demotivated to put them into non-witness data (e.g.
outputs) - which make vast majority of a simple, genuine transaction.
As a result "blockchain" changes its nature and becomes full of
bloated witness data (e.g. a JPEG in a single transaction in a
"pathological" 4MB block) instead of simple, genuine transactions.
> inflating the UTXO set (...).
UTXO set inflates naturally as there are more and more participants.
Besides, blockspace price discrimination didn't stop it. Again, the
UTXO set size argument is irrelevant to the subject.
next prev parent reply other threads:[~2024-01-21 17:14 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 [this message]
2023-12-27 22:39 ` Keagan McClelland
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='CAMHHROzkqCVJQc7uszmtATiWWSm=WAEa2QmSxhcevCQowCyb9w@mail.gmail.com' \
--to=gregtonoski@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=bnagaev@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