From: Murch <murch@murch.one>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] [BIP Proposal] Reduced Data Temporary Softfork
Date: Sat, 8 Nov 2025 17:21:21 -0800 [thread overview]
Message-ID: <5370ae82-7abe-4790-a1ab-e1a7334ef382@murch.one> (raw)
In-Reply-To: <MQv8-Ejvo7ZUcCOQkmtFo8hOATgSrKWvtG25JqUgWXKNGYHbCkVc-IawuPcRN_BebLTLQr3QtTTaA1iWrWgs0fFwI45jnQFi5_ORnAbsP_k=@proton.me>
Hello Dathon,
On 2025-11-08 13:02, dathonohm via Bitcoin Development Mailing List wrote:
> For those who prefer viewing the proposal in a browser, I have pushed a
> copy of it to a non-PR branch, since the PR is still locked: https://
> github.com/dathonohm/bips/blob/reduced-data-v2/bip-
> %3F%3F%3F%3F.mediawiki <https://github.com/dathonohm/bips/blob/reduced-
> data-v2/bip-%3F%3F%3F%3F.mediawiki>
You may have missed that the pull request “BIP draft: Reduced Data
Temporary Softfork #2017” was unlocked¹ at 2025-11-08T13:22Z, almost
exactly 12h ago at the time of writing. The accompanying comment² that
pointed this out, notified you explicitly by mention of your username.
Murch
¹ https://github.com/bitcoin/bips/pull/2017#event-20807801629
² https://github.com/bitcoin/bips/pull/2017#issuecomment-3506542546
--
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/5370ae82-7abe-4790-a1ab-e1a7334ef382%40murch.one.
next prev parent reply other threads:[~2025-11-09 1:40 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
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 [this message]
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=5370ae82-7abe-4790-a1ab-e1a7334ef382@murch.one \
--to=murch@murch.one \
--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