Jan 1, 2025

So we start with the normal form at 19.4GiB and optimize down to 12.2GiB, and have search-free access to all prevouts and required metadata for confirmation. For every block we validate, we confirm that each prevout is in a candidate block by chasing the prevout.tx->strong_tx. If the strong_tx is not found there is a possibility of a duplicate tx having been stored, one for the strong candidate block and one discovered in the validation search. In this case the full set of txs with that hash much be search. This is extremely rare but must be covered (never happens in pure uninterrupted block sync/validation but may happen with unconfirmed txs, reorganizations, or disk full stops).