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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/79f4f7d0-e13e-4dfc-8e0b-82c3488b7ffb%40dashjr.org.
