public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Ori Newman <orinewman1@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] RE BIP 300: 26% censoring attack
Date: Tue, 6 Oct 2026 14:05:36 -0700 (PDT)	[thread overview]
Message-ID: <2e554c89-a2a1-4bcf-941c-32f6a8ba9567n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1859 bytes --]

It seems like a 26% attacker can censor BIP 300 bundles indefinitely:

Assume some drivechain publishes a valid bundle, the attacker can send 
ALARM messages in all of her blocks to reduce its score by 1 in each block. 
Since the expected score increase per block is 0.74 - 0.26 = 0.48, its 
expected score in the 26300 block window is 0.48 * 26300 = 12624, which is 
less than the required score of 13150, so the bundle will almost certainly 
fail (this is only an approximation, since hitting the 13150 wall at any 
point is enough for the bundle to get accepted).

I think the fix to it should be quite simple: once we forbid ALARM messages 
or any kind of downvote, we can revert to the honest majority security 
assumption - a proposal with 51% support will almost certainly succeed to 
pass the threshold, and a proposal with 49% support will almost certainly 
fail to pass it.

If this is intentional, I suggest changing the BIP to reflect the 75% 
honest majority assumption, since this is a strong deviation from Bitcoin's 
security model (one argument for it would be to make it extra difficult for 
an attacker with less than 75% of the hashrate to steal funds). If this is 
not intentional, I suggest to forbid ALARM messages or any kind of 
downvote, so we revert to the 50% honest majority security assumption - a 
proposal with 51% support will almost certainly succeed to pass the 
threshold, and a proposal with 49% support will almost certainly fail to 
pass it.

-- 
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/2e554c89-a2a1-4bcf-941c-32f6a8ba9567n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2274 bytes --]

                 reply	other threads:[~2026-10-06 21:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2e554c89-a2a1-4bcf-941c-32f6a8ba9567n@googlegroups.com \
    --to=orinewman1@gmail.com \
    --cc=bitcoindev@googlegroups.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