public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Sjors Provoost <sjors@sprovoost.nl>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Censorship Resistant Transaction Relay - Taking out the garbage(man)
Date: Tue, 3 Jun 2025 17:41:51 +0000	[thread overview]
Message-ID: <aD8z34hk6IQ21cSv@petertodd.org> (raw)
In-Reply-To: <4BA2B86E-3E4B-416B-9237-AFD66FC4E37A@sprovoost.nl>

[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]

On Tue, Jun 03, 2025 at 08:50:34AM +0200, Sjors Provoost wrote:
> Or people can just spin up more Libre Relay nodes. Both miners and issuers of various scam tokens have a monetary incentive to do that. Whereas proponents of filters are (so far) not willing to invest serious money. E.g. when I challenged Luke Dashjr in an earlier post to reorg a single block with spam, he didn't respond [1]. Worse, Ocean proactively offers "Core" [0] templates. Although running a node is cheap, if this becomes an arms race, the side that actually spends money has the advantage.

I need to point out that you're being unfair to Ocean here: with their <1% hash
power it's damn near impossible for them to reorg blocks. The reason is because
if there are two blocks at the same height, Bitcoin Core accepts the first
block seen.

Thus if Ocean wants to reorg a "spam" block out, they need to find not just
one, but two blocks in a row before any other miner finds one. The probability
of that happening is (very) roughly 1% * 1% = 0.01% per attempt. Given that
blocks are worth ~$300k these days, you're asking them to spend tens of
millions of dollars worth of hash power just to reorg out a single block.

It's not going to happen.

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

-- 
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/aD8z34hk6IQ21cSv%40petertodd.org.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2025-06-03 18:29 UTC|newest]

Thread overview: 12+ 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-05 12:16         ` Peter Todd
2025-06-03 17:41       ` Peter Todd [this message]
2025-06-03 17:51         ` Sjors Provoost
2025-06-03 20:32           ` Sjors Provoost
2025-06-03 17:58     ` Peter Todd
2025-06-04 20:16       ` Chris Guida
2025-06-05 11:59         ` Peter Todd

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=aD8z34hk6IQ21cSv@petertodd.org \
    --to=pete@petertodd.org \
    --cc=bitcoindev@googlegroups.com \
    --cc=sjors@sprovoost.nl \
    /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