Using a storage engine without UTXO-index



Summary:

The email conversation between Gregory Maxwell and Tomas discusses the resource costs and latency-related costs in Bitcoin Core. Resource cost is not just a measure of storage requirement, but data that needs to be accessed during peak load induces more cost than data only used during base load or rarely used. The aggregate resource usage for users depends significantly on outputs rather than inputs in transactions in a block. In Core, when a block comes, the inputs are checked against the UTXO set to verify order, even if pre-synced. However, in bitcrust, it is checked against the spend-tree. Although UTXO data is always a resource cost for script validation, the ratio of different costs is not necessarily identical across implementations. Bitcrust has a slower peak load verification if the last few blocks contain many inputs, which is not the case in Core.


Updated on: 2023-06-11T23:51:23.518858+00:00