public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Nagaev Boris <bnagaev@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: Tue, 16 Jan 2024 20:40:12 -0300	[thread overview]
Message-ID: <CAFC_Vt7EKhipSECtpa87fx5Ff1eFwfjn19P=9GONOcXFFhQYOA@mail.gmail.com> (raw)
In-Reply-To: <CAMHHROwP8guVcy3yV09B=PYQscTcnGtNGMheFdvJM4ZYdWTSYw@mail.gmail.com>

On Sun, Jan 14, 2024 at 10:21 AM Greg Tonoski via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> > > 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?
>
> "Should" in order to avoid hazard of centralization. A single bidder
> who takes advantage of "buy 1 get 3 megabytes free" may outcompete a
> number of individuals whose simple transactions recieve
> anti-preferential treatment - "buy 1 get 0.33 megabytes free" in
> aggregate. There is the illustration at:
> "https://gregtonoski.github.io/bitcoin/segwit-mispricing/Comparison_of_4MB_and_1.33MB_blocks_in_Bitcoin.pdf".

It is not sufficient to be a centralized sender to utilize this
advanage. The sender has to store data in the blockchain which itself
is not the best utilization of money, even given the discount. Also
what is the danger of centralization of such senders? The dangerous
centralization is the centralization of real bitcoin sending, which
has already happened - exchanges utilize batch transaction sending,
saving on fees over a regular bitcoin sender, because they avoid
change creation. This has nothing to do with witness discount, though.

> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev



-- 
Best regards,
Boris Nagaev


  reply	other threads:[~2024-01-16 23:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27 16:44 [bitcoin-dev] [BUG]: Bitcoin blockspace price discrimination put simple transactions at disadvantage 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
2024-01-14 13:10   ` Greg Tonoski
2024-01-16 23:40     ` Nagaev Boris [this message]
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='CAFC_Vt7EKhipSECtpa87fx5Ff1eFwfjn19P=9GONOcXFFhQYOA@mail.gmail.com' \
    --to=bnagaev@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=gregtonoski@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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