From: Nagaev Boris <bnagaev@gmail•com>
To: Chris Guida <chrisguida@gmail•com>
Cc: Anthony Towns <aj@erisian•com.au>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Relax OP_RETURN standardness restrictions
Date: Thu, 1 May 2025 16:33:25 -0300 [thread overview]
Message-ID: <CAFC_Vt6Tv73tuF20MPpC7MiA5n6TfUwj+SOacCMTT=9roHkKAw@mail.gmail.com> (raw)
In-Reply-To: <CAAANnUxnEfO7VexaK_V+Rc1ZG8tO1pLAU0gsDJb8C82hiwgQ-Q@mail.gmail.com>
On Thu, May 1, 2025 at 2:20 AM Chris Guida <chrisguida@gmail•com> wrote:
> >Fees are under 3sat/vb; there's no attack. Excess block space is being
> filled by low-value spam, but that's expected and, in a permissionless
> system, unavoidable.
>
> This is just a temporary cease-fire while the spammers reload their ammunition. There is obviously about to be another wave, otherwise what is the point of eliminating OP_RETURN restrictions?
If they use OP_RETURN instead of putting data into the witness, they
will exhaust their funds four times faster and store four times less
data on the blockchain. Maybe the removal of OP_RETURN constraints in
policy is a Trojan horse against spammers?
--
Best regards,
Boris Nagaev
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAFC_Vt6Tv73tuF20MPpC7MiA5n6TfUwj%2BSOacCMTT%3D9roHkKAw%40mail.gmail.com.
next prev parent reply other threads:[~2025-05-01 22:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 18:52 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-04-18 12:03 ` Sjors Provoost
2025-04-18 12:54 ` Greg Sanders
2025-04-18 13:06 ` Vojtěch Strnad
2025-04-18 13:29 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-04-18 21:34 ` Antoine Riard
2025-04-20 8:43 ` Peter Todd
2025-04-26 9:50 ` Luke Dashjr
2025-04-26 10:53 ` Sjors Provoost
2025-04-26 11:35 ` Luke Dashjr
2025-04-26 11:45 ` Sjors Provoost
2025-04-26 12:48 ` Pieter Wuille
2025-04-28 16:20 ` Jason Hughes (wk057)
2025-04-29 14:51 ` Sjors Provoost
2025-04-30 15:37 ` Nagaev Boris
2025-04-30 16:30 ` Sjors Provoost
2025-04-29 19:20 ` Martin Habovštiak
2025-04-30 0:10 ` Jason Hughes
2025-05-01 17:40 ` Andrew Toth
2025-04-30 5:39 ` Chris Guida
2025-04-30 16:37 ` Anthony Towns
2025-05-01 4:57 ` Chris Guida
2025-05-01 19:33 ` Nagaev Boris [this message]
2025-05-02 6:34 ` Anthony Towns
2025-05-01 3:01 ` Anthony Towns
2025-05-01 22:40 ` [bitcoindev] " 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-05-02 0:14 ` PandaCute
2025-05-02 11:16 ` [bitcoindev] " Sjors Provoost
2025-05-02 6:29 ` [bitcoindev] " Greg Maxwell
2025-05-02 9:51 ` Anthony Towns
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_Vt6Tv73tuF20MPpC7MiA5n6TfUwj+SOacCMTT=9roHkKAw@mail.gmail.com' \
--to=bnagaev@gmail$(echo .)com \
--cc=aj@erisian$(echo .)com.au \
--cc=bitcoindev@googlegroups.com \
--cc=chrisguida@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