From: Jonathan Voss <k98kurz@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: The Cat, BIP draft discussion.
Date: Wed, 17 Dec 2025 08:22:51 -0800 (PST) [thread overview]
Message-ID: <4e947f47-b43d-4ec3-ac6a-aa66ea0cfb79n@googlegroups.com> (raw)
In-Reply-To: <CAAS2fgTjF_e5vLEzp672_jmF82jDUre0wcZKHB5my8kTdFOGgw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1614 bytes --]
This is my third attempt to respond to this. Idk what is going wrong here.
The problem with dropping Bitcoin Stamps UTXOs from the UTXO set without a
consensus change is that a clever use of steganography could cause one of
those otherwise unspendable outputs to be spendable, thus causing a fork
between those nodes that adopted the Stamp pruning method and those that
did not once one of those steganographic Stamps is spent. Though this is
unlikely, it is still technically possible, and I would not put it past the
denizens of the Internet to stir up trouble just for its own sake.
On Friday, December 12, 2025 at 6:49:41 PM UTC-5 Greg Maxwell wrote:
> On Fri, Dec 12, 2025 at 9:26 PM Jonathan Voss <k98...@gmail.com> wrote:
>
>> Since the Bitcoin Stamps outputs are already unspendable, it makes
>> perfect sense to mark and drop them from the UTXO set.
>
>
> There is no consensus change involved in not storing a provably
> unspendable output, it's just an implementation detail with no
> interoperability implications and doesn't need a BIP. Bitcoin core has
> long done so for several types of unspendable outputs, e.g. outputs over
> 10kb and ones starting with OP_RETURN.
>
>
--
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/4e947f47-b43d-4ec3-ac6a-aa66ea0cfb79n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2436 bytes --]
next prev parent reply other threads:[~2025-12-19 1:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32f8c689-314d-4a5e-9af6-2e3e704582e6n@googlegroups.com>
[not found] ` <CAAS2fgRR77nZj3-rJo70dnxe8Lma88-C9JqdVTYfXGHRgFu3pA@mail.gmail.com>
2025-12-11 20:54 ` [bitcoindev] " Bitcoin Mechanic
2025-12-12 1:49 ` TwoLargePizzas
2025-12-13 15:02 ` Greg Maxwell
2025-12-14 1:51 ` Pepe Hodler
2025-12-15 10:35 ` Nona YoBidnes
2025-12-15 16:04 ` Greg Maxwell
2025-12-12 17:13 ` [bitcoindev] " Jonathan Voss
2025-12-12 23:40 ` Greg Maxwell
2025-12-13 3:54 ` Melvin Carvalho
2025-12-13 7:07 ` Ataraxia 009
2025-12-17 16:22 ` Jonathan Voss [this message]
2025-12-19 3:31 ` Greg Maxwell
2025-12-21 5:07 ` John
2025-12-23 19:12 ` Greg Maxwell
2025-12-24 17:19 ` waxwing/ AdamISZ
2025-12-30 14:36 ` Antoine Riard
2026-01-19 1:11 ` Pepe Hodler
2026-01-23 3:45 ` Chris Riley
2026-01-23 13:55 ` Galois Field
2026-01-22 1:14 ` Claire Ostrom
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=4e947f47-b43d-4ec3-ac6a-aa66ea0cfb79n@googlegroups.com \
--to=k98kurz@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