Create lmdb unit tests

[SWvheerden]

Bounty: Create LMDB Unit Tests

Tier: M — 60,000 XTM

Description

LMDB correctness in the base node is currently untested. Create a reproducible test chain (genesis block, 10 main-chain blocks, and a 10-block fork from block 5) and write two unit tests: one that writes the chain to a new LMDB file and bit-compares it against a reference, and one that loads the LMDB file and verifies all headers, blocks, outputs, inputs, kernels, and accumulated data can be fetched correctly through the full range of query methods.

Acceptance Criteria

• A test chain is created with a genesis block, 10 main-chain blocks, and a 10-block fork from block 5
• All block data is saved in a JSON file for reproducibility
• A write test creates a new LMDB file from the JSON data and bit-compares it against the reference file
• A read test loads the LMDB file and verifies all 15 main-chain headers, 5 reorged headers, and all blocks can be fetched
• The read test verifies per-block queries: outputs by header_hash, inputs by header_hash, kernels by header_hash, output by hash, unspent output by commitment, output by payref, outputs with spend state at height, kernel by excess sig, and header containing kernel by MMR position

Context

• Issue opened by @SWvheerden
• An earlier attempt (PR Add LMDB blockchain unit tests (write + read) #7716 by Copilot agent) was closed; this bounty is for a human-quality implementation
• Relevant code: base_layer/core/src/chain_storage/lmdb_db/

How to Claim

1. Comment on this issue to signal intent (courtesy, not a lock)
2. Fork the repo and do the work
3. Submit a PR that meets the acceptance criteria
4. First PR that passes review and gets merged wins the bounty
5. On acceptance, XTM payment is processed

Notes

• AI-assisted development is expected and encouraged
• If you get stuck, ask in Discord
• If you can't complete it within 14 days of claiming, let us know so someone else can pick it up

[SWvheerden]

Description

LMDB correctness is currently untested. We need to create a test chain and then write two unit tests to validate that LMDB read/write operations work correctly.

Create chain

We should create a chain with the following steps:

• Add a genesis block
• Create a test chain of 10 blocks, spending inputs from the previous blocks, added in order
• Create another chain forking from block 5 for 10 more blocks, spending inputs from the previous blocks, added in order
• Save all block data in a JSON file so we can replicate this
• Save the LMDB file

Test write

Validate LMDB writing by:

• Reading all JSON data from the original chain creation and following the chain creation steps
• Creating a new LMDB file and doing a bit-compare to verify the write is identical

Test read

Validate LMDB reading by:

• Reading the JSON file for each block
• Loading up the test LMDB file as the database
• Testing if you can fetch all 15 main chain headers
• Testing if you can fetch all 5 reorged headers
• Testing if you can fetch all 15 main chain blocks
• Fetching the accumulated data for each mainnet block and orphan
• Testing if you can fetch all 5 reorged blocks
• For each mainnet block, testing:
  • Fetch outputs in a block by header_hash
  • Fetch inputs in a block by header_hash
  • Fetch kernels in a block by header_hash
  • Fetch an output by hash (fetch_output)
  • Fetch an unspent output by commitment (fetch_unspent_output_hash_by_commitment)
  • Fetch an output by payment reference (fetch_mined_info_by_payref)
  • Fetch outputs with spend state at a given height (fetch_outputs_in_block_with_spend_state)
  • Fetch kernel by excess signature (fetch_kernel_by_excess_sig)
  • Fetch header containing a kernel by MMR position (fetch_header_containing_kernel_mmr)

Acceptance criteria

• A test chain is created with a genesis block, 10 main-chain blocks, and a 10-block fork from block 5
• All block data is saved in a JSON file for reproducibility
• A write test creates a new LMDB file from the JSON data and bit-compares it against the reference
• A read test loads the LMDB file and verifies all headers, blocks, outputs, inputs, kernels, and accumulated data can be fetched correctly (see detailed list above)

Size: M

[metalaureate]

Original issue description (preserved before bounty rewrite)

We need to create 2 tests to ensure lmdb is correct
1: Write all blockchain data, and test all blockchain functionality to a new lmdb file
2 Load all blockchain data and see if we can read this.

We need to create a new blockchain, with a few blocks, and run through a few operations such as adding inputs, outputs, kernels, pruning etc.
We can use a single function to do this, and we can then for 1, do a bit compare on the generated files, and we can also use this function to generate the file we use to compare against

Size: M

[0xPepeSilvia]

Claiming this bounty. Will have a PR up within the 14-day window.