Bitcoin full node and query server

Apr 18, 2024

View in context in the libbitcoin Slack #general mirror.

evoskuil13:31

Writing confirmation state adds somewhat to this, though that would be more like 30 additional minutes.

Just did a full run with confirmation state written following evaluation and there was no material increase in cost, under 3 hours. So assuming that runs sequentially that would be a minimum full chain (no milestones or checkpoints) validation cost.

💯 1

evoskuil18:24

In any case, it's a very positive data point. The confirmation is extremely costly in theory. You must mark each output (or its tx) as confirmed, and must mark each spending input as confirmed (or its tx), ensure that when you spend you are only spending outputs that exist, and are confirmed in tx of a block height at/previous to the input tx, and must ensure that they are not previously spent by a confirmed block tx. Then there are coinbase maturity checks (spender must be > 100 blocks from coinfirmed cb height), and finally relative locktime checks (bip68), which require the height and mtp of spender and spent, as well as spender tx.sequence.