Bootstrap UTXO Module

[lowhung]

Context

The UTXO State module tracks unspent transaction outputs (UTXOs) by processing UTXO delta messages. It currently expects delta messages starting from genesis. During bootstrap, it instead needs to load the complete UTXO set from snapshot's utxo_state.

Problem

When bootstrapping from a snapshot (e.g., epoch 500), the UTXO state module needs to initialize the complete UTXO set rather than replaying all transactions from genesis. The snapshot provides millions of UTXOs that must be loaded efficiently into our stores (cough batching cough ;)).

Acceptance Criteria

• UTXO state initializes from snapshot data during bootstrap
• Normal delta processing continues after bootstrap
• Bootstrap data can be validated against Blockfrost API queries

Testing Requirements

• UTXO queries return correct data after bootstrap / Blockfrost API queries match bootstrap data

Definition of Done

• UTXO state initializes from snapshot without replaying deltas
• All UTXOs and metadata accurate after bootstrap
• UTXO queries work correctly after bootstrap
• Blockfrost API validation confirms correctness

[alexwoods]

This is currently blocked by a difference in how we store utxos in the utxo store module vs. what we get from the Amaru snapshot. The utxo store keys utxos by UTxOIdentifier which is a combination of block, tx index and txout index. None of that information is available in the Amaru snapshot for utxos, so we currently have no way to bootstrap the utxo store