From: Luke Dashjr <luke@dashjr•org>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] The Tragic Tale of BIP30
Date: Sun, 27 Apr 2025 14:20:44 -0400 [thread overview]
Message-ID: <79f4f7d0-e13e-4dfc-8e0b-82c3488b7ffb@dashjr.org> (raw)
In-Reply-To: <CAPv7TjZTWhgzzdps3vb0YoU3EYJwThDFhNLkf4XmmdfhbORTaw@mail.gmail.com>
On 4/27/25 12:45, Ruben Somsen wrote:
> #### Solution B
Solution C could be to remove it, but restore the previous UTXO. In
other words, treat the overwrite as a spend of the overwritten transaction.
Solution D could be to simply not create the UTXOs later overwritten
when they are first seen.
> Given that we have no duplicates, barring the two exceptions, we could
> replace the inefficient BIP30 UTXO set check with a coinbase
> uniqueness check. We simply cache the coinbase TXIDs and ensure there
> are no duplicates. Doing this until block 227931 results in a modest
> ~7MB cache.
And additional CPU time to check the txids against 7 MB instead of 64
bytes. Sounds strictly worse than how we're handling it today...?
--
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/79f4f7d0-e13e-4dfc-8e0b-82c3488b7ffb%40dashjr.org.
next prev parent reply other threads:[~2025-04-27 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 16:45 Ruben Somsen
2025-04-27 18:20 ` Luke Dashjr [this message]
2025-04-27 18:30 ` eric
2025-04-27 21:01 ` eric
2025-04-28 11:48 ` Sjors Provoost
2025-04-28 12:39 ` Eric Voskuil
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=79f4f7d0-e13e-4dfc-8e0b-82c3488b7ffb@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoindev@googlegroups.com \
/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