Author: Gregory Maxwell 2015-02-20 18:20:59
Published on: 2015-02-20T18:20:59+00:00
In a conversation between Adam Back and an unknown person, the use of "UTXO set" was deemed confusing as it may suggest the complete verification state. Instead, it refers to block-local data which avoids large IO overheads. The concept is straightforward - there is a scriptpubkey bitmap per block which is committed. Users can request the map and feel confident that they have received a faithful one. If there are hits, they can request the block knowing that there was no censoring. It is possible to structure additional layers to the bitmap so that one can incrementally query to trade-off map size for false request overhead, but it is unclear how much of a win this would be for normal parameters. Additionally, it is possible to extract the txout list for the whole block and commit to that too. This makes it possible to request just the outputs and obtain a faithful copy of them, which is much smaller than the entire block.
Updated on: 2023-05-19T19:49:14.444320+00:00