Ledger

The Ledger is responsible for validating Blocks and represents the actual semantics of Cardano transactions. The format of blocks and transactions is defined in so-called eras: Byron, Shelley, Allegra, Mary, Alonzo, Babbage and Conway.

This blueprint is currently more of an entrypoint to already existing implementation-independent descriptions of Cardano transactions and the ledger rules. While existing work covers a lot already, the cardano-blueprint may serve as an incubation or staging area for material to cover gaps. For starters, the EUTxO Crash Course from Aiken is a very good introduction about Cardano transactions. See Transaction fee for an informal write-up on how transaction fees are currently calculated.

Ledger rules

The Formal Specification is the source of truth for ledger semantics. While it is currently being made more accessible by interleaving explanations with Agda definitions, its very dense on the Agda and actively worked on to close the gap latest era descriptions and the old era definitions. The Haskell implementation of the ledger holds a list of design documents and ledger specifications for all eras. See Block Validation for a description of the Conway era block validation rules.

Block and transaction format

The .cddl files in cardano-ledger define the wire-format of blocks and transactions for each era. These are self-contained for each era and are referenced in other blueprint CDDL schemas.

Conformance tests

Despite the formal specification provides a precise definition for semantics, testing the behavior of ledger implementations against the specification and also the ledger implementations against each other is crucial. For this purpose, a conformance test suite with implementation-independent test vectors can be used.