From: Peter Todd <pete@petertodd•org>
To: Greg Maxwell <gmaxwell@gmail•com>
Cc: Sjors Provoost <sjors@sprovoost•nl>, bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Censorship Resistant Transaction Relay - Taking out the garbage(man)
Date: Thu, 5 Jun 2025 12:16:59 +0000 [thread overview]
Message-ID: <aEGKu4u8B03Tiy26@petertodd.org> (raw)
In-Reply-To: <CAAS2fgT3gyra4BNN1zDVz=n=tmteZLC4xuzTWSm_s0T6Rw2MJA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3126 bytes --]
On Tue, Jun 03, 2025 at 05:00:42PM +0000, Greg Maxwell wrote:
> But when the censorship is backed by threat (even if vague or
> unconstitutional) of civil or criminal legal penalties, the avenue to just
> bypass may be much less available.
>
> So for example, in an alternative universe: Bitcoin goes along with Guida
> and after having built this massive edifice of transaction censorship the
> Bitcoin developers lose their UK lawsuit Craig S Wright after he
> successfully bribes a judge, and now have a the UK courts imposing a
> worldwide order to freeze any of their bitcoin address under threat of
> imprisonment. The censorship is deployed via the prebuilt censorship
> infrastructure, and willingness to bypass it is greatly decreased because
> doing so would land the bypasser a UK arrest warrant. Could they still get
> their transactions through? Probably but at much greater costs and delays,
> creating a significant harm. Not building the censorship infrastructure
> (even though you intend it for 'good' purposes) and instead building
> anti-censorship infrastructure leaves us all with a better world.
I want to emphasize that this type of threat is not theoretical.
Court-Confirmed Fraudster Craig Wright did in fact sue us in an effort to
recover alleged stolen coins. If courts perceive a history of Bitcoin Core
developers actively trying to prevent "undesirable" transactions, then there is
a very real chance for courts to order Bitcoin Core developers to do things
like freeze addresses, even though if anyone posted such a pull request it
would be ineffectual because people wouldn't choose to run it. Still the order
would be highly disruptive to people and the project. The community should want
every protection available to prevent future court actions like that from being
considered, issued or succeeding. A history of actively trying to prevent
"undesirable" transactions does not help.
It's notable that this advocacy from filtering is coming from a pool that
claims to offer decentralized mining via the DATUM protocol. Yet hasn't even
taken the most basic step to actually achieving that: releasing the full DATUM
source code. If a court orders miners to run an extension of Knots with
specific addresses censored, DATUM will do absolutely nothing to stop that:
DATUM currently has OCEAN approving blocks - allowing OCEAN to reject shares
mining censored addresses. Without the ability to spin up competitors to OCEAN,
miners wishing to contribute uncensored hash power can do nothing other than
hope someone decided to rewrite, from scratch, all the closed-source OCEAN code
making DATAUM actually work.
If you're actually serious about decentralization, open-source OCEAN.
--
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/aEGKu4u8B03Tiy26%40petertodd.org.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-06-05 12:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 11:16 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 [this message]
2025-06-03 17:41 ` Peter Todd
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=aEGKu4u8B03Tiy26@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoindev@googlegroups.com \
--cc=gmaxwell@gmail$(echo .)com \
--cc=sjors@sprovoost$(echo .)nl \
/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