From: Jameson Lopp <jameson.lopp@gmail.com>
To: dathonohm@proton.me
Cc: "bitcoindev@googlegroups.com" <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] [BIP Proposal] Reduced Data Temporary Softfork
Date: Sun, 26 Oct 2025 16:47:57 -0400 [thread overview]
Message-ID: <CADL_X_caKFvypdDa2k-Hhy1QCMJgnb6Rc8i0vBRW9=yoq4h2ZA@mail.gmail.com> (raw)
In-Reply-To: <AWiF9dIo9yjUF9RAs_NLwYdGK11BF8C8oEArR6Cys-rbcZ8_qs3RoJURqK3CqwCCWM_zwGFn5n3RECW_j5hGS01ntGzPLptqcOyOejunYsU=@proton.me>
[-- Attachment #1: Type: text/plain, Size: 2657 bytes --]
It's quite clear from the PR discussion that there are a multitude of
contentious issues at play with this proposal.
Even aside from all of the technical concerns, the underlying implication
of using legal coercion to require miners and other network participants to
comply with arbitrary legal and moral frameworks makes it a non-starter in
my opinion.
On Sun, Oct 26, 2025 at 3:43 PM dathonohm via Bitcoin Development Mailing
List <bitcoindev@googlegroups.com> wrote:
> Hi list -
>
> Due to Bitcoin Core v30 gaining in popularity, it has become necessary to
> move forward on luke-jr's ML proposal
> <https://github.com/bitcoin/bips/pull/2017> to temporarily limit
> arbitrary data at the consensus level, which so far has 3 weeks with no
> objections:
> https://github.com/bitcoin/bips/pull/2017
>
> The idea is to strongly re-affirm in consensus that bitcoin is money, not
> data storage. It is implemented as a temporary softfork that can activate
> in one of two different ways: proactive, or reactive.
>
> After a year, the soft fork expires, giving us time to come up with a more
> permanent solution.
>
> The timeline is a bit tight, but I think everyone has incentives to
> support a quick and orderly activation.
>
> Please feel free to leave a comment on the PR or reach out to me over
> email with any feedback.
>
> There is much work still to do, so if you have some technical skills and
> would like to join in the effort with dev/testing, please reach out as well.
>
> Bitcoin is money.
>
> Sincerely,
>
> Dathon Ohm
>
> --
> 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/AWiF9dIo9yjUF9RAs_NLwYdGK11BF8C8oEArR6Cys-rbcZ8_qs3RoJURqK3CqwCCWM_zwGFn5n3RECW_j5hGS01ntGzPLptqcOyOejunYsU%3D%40proton.me
> <https://groups.google.com/d/msgid/bitcoindev/AWiF9dIo9yjUF9RAs_NLwYdGK11BF8C8oEArR6Cys-rbcZ8_qs3RoJURqK3CqwCCWM_zwGFn5n3RECW_j5hGS01ntGzPLptqcOyOejunYsU%3D%40proton.me?utm_medium=email&utm_source=footer>
> .
>
--
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/CADL_X_caKFvypdDa2k-Hhy1QCMJgnb6Rc8i0vBRW9%3Dyoq4h2ZA%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 4384 bytes --]
next prev parent reply other threads:[~2025-10-26 20:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 20:43 dathonohm via Bitcoin Development Mailing List
2025-10-26 20:47 ` Jameson Lopp [this message]
2025-10-27 4:22 ` dathonohm via Bitcoin Development Mailing List
2025-10-27 12:14 ` Jameson Lopp
2025-10-27 16:35 ` TheWrlck
2025-10-26 22:27 ` Peter Todd
2025-10-27 3:41 ` Jal Toorey
2025-10-27 17:27 ` Max
2025-10-27 4:08 ` dathonohm via Bitcoin Development Mailing List
2025-10-27 18:29 ` Kyle Stout
2025-10-27 19:56 ` Greg Maxwell
2025-10-28 5:13 ` dathonohm via Bitcoin Development Mailing List
2025-10-30 0:31 ` Antoine Riard
2025-10-30 2:43 ` Erik Aronesty
2025-11-08 0:51 ` dathonohm via Bitcoin Development Mailing List
2025-11-08 3:43 ` Edil Guimarães de Medeiros
2025-11-08 9:30 ` 'Bitcoin Eagle' via Bitcoin Development Mailing List
2025-11-08 15:38 ` Greg Maxwell
2025-11-08 16:40 ` Daniel Buchner
2025-11-08 17:55 ` Chris Riley
2025-11-08 21:02 ` dathonohm via Bitcoin Development Mailing List
2025-11-08 21:39 ` Greg Maxwell
2025-11-09 20:07 ` dathonohm via Bitcoin Development Mailing List
2025-11-11 7:43 ` 'Bitcoin Eagle' via Bitcoin Development Mailing List
2025-11-11 16:23 ` Greg Maxwell
2025-11-09 1:21 ` Murch
2025-11-09 20:56 ` onyxcoyote
2025-11-09 21:34 ` Peter Todd
2025-11-10 19:46 ` Lucas Barbosa
2025-10-28 9:16 ` /dev /fd0
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='CADL_X_caKFvypdDa2k-Hhy1QCMJgnb6Rc8i0vBRW9=yoq4h2ZA@mail.gmail.com' \
--to=jameson.lopp@gmail.com \
--cc=bitcoindev@googlegroups.com \
--cc=dathonohm@proton.me \
/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