From: Lazy Fair <laissez.faire.btc@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Cc: murch@murch.one
Subject: [bitcoindev] Safe Redaction: an early draft BIP
Date: Tue, 30 Dec 2025 17:37:40 +1100 [thread overview]
Message-ID: <CABHzxrisM-wX_M_DRp3W1rjddAb_ATbXU0cXXpEu_ht9i2NEwQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]
Hello list,
I've prepared a draft BIP for community feedback, called Safe Redaction (
https://github.com/laissez-faire-btc/safe-redaction/blob/main/bip-safe-redaction.md).
It proposes a soft fork that gives node operators the option to redact
arbitrary data that they find objectionable, while maintaining the benefits
of running a full node.
Please note that I have used BIP 3 for this draft - for a couple of
reasons. First and foremost, BIP 3 is likely to be adopted before Safe
Redaction, so this is basic future-proofing. Additionally, this may be the
first time BIP 3 has been used to draft a new BIP, and so this may add
constructive support for the adoption of BIP 3, or highlight issues, or
simply help to raise awareness and progress the discussion.
As described in BIP 3, the purpose of this email is to invite BIP editors
and other community members to comment on the proposal, in regard to:
* Novelty of the idea
* Viability, utility, and relevance of the concept
* Readiness of the proposal
* On-topic for the Bitcoin community
Of course, I am also keen to hear any and all thoughts on this proposal,
from any perspective. Community interest is a requirement for any new BIP,
so if you are interested, please speak up.
If you would like to have a more in-depth conversation than this
distribution list can practically support, you are invited to join the
Discord server. The latest invite link is in the draft BIP, linked above.
You can also email me details of your preferred mode of private
communication, if necessary.
Thank you.
Laissez faire, laissez passer.
Let it be, let it go.
--
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/CABHzxrisM-wX_M_DRp3W1rjddAb_ATbXU0cXXpEu_ht9i2NEwQ%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2925 bytes --]
reply other threads:[~2026-01-12 0:37 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=CABHzxrisM-wX_M_DRp3W1rjddAb_ATbXU0cXXpEu_ht9i2NEwQ@mail.gmail.com \
--to=laissez.faire.btc@gmail.com \
--cc=bitcoindev@googlegroups.com \
--cc=murch@murch.one \
/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