Module ledger_db

Implements a wrapper around RocksDB meant for storing rollup history (“the ledger”). This wrapper implements helper traits for writing blocks to the ledger, and for serving historical data via RPC

Structs

ItemNumbers

A SlotNumber, BatchNumber, TxNumber, and EventNumber which are grouped together, typically representing the respective heights at the start or end of slot processing.

LedgerDB

A database which stores the ledger history (slots, transactions, events, etc). Ledger data is first ingested into an in-memory map before being fed to the state-transition function. Once the state-transition function has been executed and finalized, the results are committed to the final db

SlotCommit

All of the data to be committed to the ledger db for a single slot.