From: Sjors Provoost <sjors@sprovoost.nl>
To: Chris Guida <chrisguida@gmail.com>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Censorship Resistant Transaction Relay - Taking out the garbage(man)
Date: Thu, 5 Jun 2025 15:29:17 +0200 [thread overview]
Message-ID: <05CE1FD4-3BE1-4F80-829F-684E20BA73D4@sprovoost.nl> (raw)
In-Reply-To: <CAAANnUyCj2cAgAG-sDZi_xOHHoEf7YO10f4XdKmSZCEDC=Fx6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3767 bytes --]
Hi Chris,
I'm replying to a few points that matter imo.
> Again, as I tried to emphasize in my prior message, the goal is not to censor; the goal is to rate-limit spam.
.
The tooling you're building is dual-use at best, and from a miner point of view it's censorship.
>> Then all you've achieved is an incentive to submit directly to miners, making those miners more profitable. Congrats, you didn't fix spam, you didn't rate limit anything and you made mining more centralised.
>
>
> Again, if miners are doing this, then they are hostile. If >50% of miners are hostile, then we need to know right now because Nakamoto Consensus falls apart if >50% of the hashrate is dishonest.
Miners are simply following their incentives. It's merely your opinion that this is "hostile". The people who share your opinion have not presented a credible way of enforcing it. All they've achieved is collateral damage.
> Is your concern that the USG would spin up a bunch of GM nodes that don't relay transactions from OFAC addresses?
No, they would take down the entire mempool by spinning up a million well connected fake nodes that behave in the same way your project does, except they drop *all* transactions. Since there's no financial incentive for users to run nodes, it'll be hard to counter this attack by merely spinning up more nodes.
> >You speak of "rate limiting", but delaying propagation doesn't rate limit anything. Unless you completely block some percentage of transactions, the same amount of spam ends up in blocks, just a little bit later. The rate, e.g. gigabytes per months, stays the same.
>
> Again, this is simply incorrect. Spam does not have inelastic demand.
> [...]
> If a certain percentage of the hashrate is confirming spam, let's say 20%,
No, 100% will be confirming spam and nothing happens to the fee rate. Elasticity isn't an issue here.
Where does your 20% figure come from? Is that based on your assumption they are not "hostile" and would just go along with not receiving the extra revenue if your sybil nodes block it?
But why would 80% of miners throw away fee revenue? They won't, so both transaction makers and miners will go around your "rate limiting".
The thing that is concerning here is that they'll use centralised transaction submission services for this, and any miner that doesn't join such service loses revenue and goes out of business.
> >Whereas proponents of filters are (so far) not willing to invest serious money.
>
> I wouldn't be so sure about that.
You're not providing any evidence to the contrary.
And again, Ocean Pool proactively added the "Core" template after they got pushback from customers for only offering Knots with filtering. After v30 that template will allow unlimited OP_RETURN. Perhaps they'll drop it then, but so far they haven't put a cent of revenue at risk.
> >Or people can just spin up more Libre Relay nodes.
>
> Who are these people? Altcoiners?? Yeah, right. Anyway, we can just spin up more GM nodes.
This comes back to question of budget. Miners and scammers have budget for relay infrastructure. You can of course try to outspend them, with your own money or a rich donor. If you sustain that effort long enough, it may be cheaper for them to use centralised submission services. Which as others have pointed out is very bad.
- Sjors
--
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/05CE1FD4-3BE1-4F80-829F-684E20BA73D4%40sprovoost.nl.
[-- Attachment #2: Type: text/html, Size: 5122 bytes --]
next prev parent reply other threads:[~2025-06-09 10:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 11:16 [bitcoindev] Censorship Resistant Transaction Relay - Taking out the garbage(man) Peter Todd
2025-05-27 11:37 ` John Carvalho
2025-06-03 2:52 ` Chris Guida
2025-06-03 6:50 ` Sjors Provoost
2025-06-03 17:00 ` Greg Maxwell
2025-06-04 20:00 ` Chris Guida
2025-06-05 12:16 ` Peter Todd
2025-06-03 17:41 ` Peter Todd
2025-06-03 17:51 ` Sjors Provoost
2025-06-03 20:32 ` Sjors Provoost
2025-06-04 18:44 ` Chris Guida
2025-06-05 13:29 ` Sjors Provoost [this message]
2025-06-03 17:58 ` Peter Todd
2025-06-04 20:16 ` Chris Guida
2025-06-05 11:59 ` Peter Todd
2025-06-06 17:38 ` Rijndael
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=05CE1FD4-3BE1-4F80-829F-684E20BA73D4@sprovoost.nl \
--to=sjors@sprovoost.nl \
--cc=bitcoindev@googlegroups.com \
--cc=chrisguida@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