Home / Input Output / cardano-ledger
Mar 24, 6-7 PM (0)
Mar 24, 7-8 PM (2)
Mar 24, 8-9 PM (1)
Mar 24, 9-10 PM (1)
Mar 24, 10-11 PM (0)
Mar 24, 11-12 AM (0)
Mar 25, 12-1 AM (0)
Mar 25, 1-2 AM (0)
Mar 25, 2-3 AM (0)
Mar 25, 3-4 AM (0)
Mar 25, 4-5 AM (0)
Mar 25, 5-6 AM (0)
Mar 25, 6-7 AM (0)
Mar 25, 7-8 AM (0)
Mar 25, 8-9 AM (0)
Mar 25, 9-10 AM (7)
Mar 25, 10-11 AM (0)
Mar 25, 11-12 PM (10)
Mar 25, 12-1 PM (13)
Mar 25, 1-2 PM (0)
Mar 25, 2-3 PM (0)
Mar 25, 3-4 PM (0)
Mar 25, 4-5 PM (2)
Mar 25, 5-6 PM (0)
Mar 25, 6-7 PM (8)
Mar 25, 7-8 PM (0)
Mar 25, 8-9 PM (0)
Mar 25, 9-10 PM (0)
Mar 25, 10-11 PM (0)
Mar 25, 11-12 AM (2)
Mar 26, 12-1 AM (0)
Mar 26, 1-2 AM (0)
Mar 26, 2-3 AM (0)
Mar 26, 3-4 AM (0)
Mar 26, 4-5 AM (0)
Mar 26, 5-6 AM (0)
Mar 26, 6-7 AM (0)
Mar 26, 7-8 AM (0)
Mar 26, 8-9 AM (0)
Mar 26, 9-10 AM (4)
Mar 26, 10-11 AM (5)
Mar 26, 11-12 PM (1)
Mar 26, 12-1 PM (3)
Mar 26, 1-2 PM (10)
Mar 26, 2-3 PM (14)
Mar 26, 3-4 PM (9)
Mar 26, 4-5 PM (3)
Mar 26, 5-6 PM (1)
Mar 26, 6-7 PM (0)
Mar 26, 7-8 PM (0)
Mar 26, 8-9 PM (0)
Mar 26, 9-10 PM (4)
Mar 26, 10-11 PM (1)
Mar 26, 11-12 AM (0)
Mar 27, 12-1 AM (0)
Mar 27, 1-2 AM (0)
Mar 27, 2-3 AM (0)
Mar 27, 3-4 AM (6)
Mar 27, 4-5 AM (5)
Mar 27, 5-6 AM (0)
Mar 27, 6-7 AM (0)
Mar 27, 7-8 AM (0)
Mar 27, 8-9 AM (0)
Mar 27, 9-10 AM (2)
Mar 27, 10-11 AM (2)
Mar 27, 11-12 PM (8)
Mar 27, 12-1 PM (2)
Mar 27, 1-2 PM (0)
Mar 27, 2-3 PM (0)
Mar 27, 3-4 PM (1)
Mar 27, 4-5 PM (3)
Mar 27, 5-6 PM (0)
Mar 27, 6-7 PM (0)
Mar 27, 7-8 PM (0)
Mar 27, 8-9 PM (2)
Mar 27, 9-10 PM (0)
Mar 27, 10-11 PM (1)
Mar 27, 11-12 AM (0)
Mar 28, 12-1 AM (0)
Mar 28, 1-2 AM (0)
Mar 28, 2-3 AM (0)
Mar 28, 3-4 AM (0)
Mar 28, 4-5 AM (0)
Mar 28, 5-6 AM (0)
Mar 28, 6-7 AM (0)
Mar 28, 7-8 AM (0)
Mar 28, 8-9 AM (0)
Mar 28, 9-10 AM (0)
Mar 28, 10-11 AM (0)
Mar 28, 11-12 PM (0)
Mar 28, 12-1 PM (0)
Mar 28, 1-2 PM (0)
Mar 28, 2-3 PM (0)
Mar 28, 3-4 PM (0)
Mar 28, 4-5 PM (0)
Mar 28, 5-6 PM (0)
Mar 28, 6-7 PM (0)
Mar 28, 7-8 PM (0)
Mar 28, 8-9 PM (0)
Mar 28, 9-10 PM (0)
Mar 28, 10-11 PM (0)
Mar 28, 11-12 AM (0)
Mar 29, 12-1 AM (0)
Mar 29, 1-2 AM (0)
Mar 29, 2-3 AM (0)
Mar 29, 3-4 AM (0)
Mar 29, 4-5 AM (0)
Mar 29, 5-6 AM (0)
Mar 29, 6-7 AM (0)
Mar 29, 7-8 AM (0)
Mar 29, 8-9 AM (7)
Mar 29, 9-10 AM (0)
Mar 29, 10-11 AM (0)
Mar 29, 11-12 PM (0)
Mar 29, 12-1 PM (5)
Mar 29, 1-2 PM (0)
Mar 29, 2-3 PM (0)
Mar 29, 3-4 PM (0)
Mar 29, 4-5 PM (0)
Mar 29, 5-6 PM (0)
Mar 29, 6-7 PM (1)
Mar 29, 7-8 PM (0)
Mar 29, 8-9 PM (0)
Mar 29, 9-10 PM (0)
Mar 29, 10-11 PM (0)
Mar 29, 11-12 AM (0)
Mar 30, 12-1 AM (0)
Mar 30, 1-2 AM (0)
Mar 30, 2-3 AM (0)
Mar 30, 3-4 AM (0)
Mar 30, 4-5 AM (0)
Mar 30, 5-6 AM (0)
Mar 30, 6-7 AM (0)
Mar 30, 7-8 AM (0)
Mar 30, 8-9 AM (0)
Mar 30, 9-10 AM (0)
Mar 30, 10-11 AM (1)
Mar 30, 11-12 PM (0)
Mar 30, 12-1 PM (2)
Mar 30, 1-2 PM (0)
Mar 30, 2-3 PM (0)
Mar 30, 3-4 PM (0)
Mar 30, 4-5 PM (0)
Mar 30, 5-6 PM (0)
Mar 30, 6-7 PM (0)
Mar 30, 7-8 PM (0)
Mar 30, 8-9 PM (0)
Mar 30, 9-10 PM (0)
Mar 30, 10-11 PM (0)
Mar 30, 11-12 AM (0)
Mar 31, 12-1 AM (0)
Mar 31, 1-2 AM (0)
Mar 31, 2-3 AM (0)
Mar 31, 3-4 AM (0)
Mar 31, 4-5 AM (0)
Mar 31, 5-6 AM (0)
Mar 31, 6-7 AM (0)
Mar 31, 7-8 AM (0)
Mar 31, 8-9 AM (0)
Mar 31, 9-10 AM (0)
Mar 31, 10-11 AM (0)
Mar 31, 11-12 PM (0)
Mar 31, 12-1 PM (0)
Mar 31, 1-2 PM (0)
Mar 31, 2-3 PM (0)
Mar 31, 3-4 PM (0)
Mar 31, 4-5 PM (0)
Mar 31, 5-6 PM (0)
Mar 31, 6-7 PM (0)
149 commits this week Mar 24, 2026 - Mar 31, 2026
Make `ContextError` constructors from Alonzo to Dijkstra era lazy
Since `ContextError`s are never stored and their reporting doesn't need
to be efficient (we always optimize for the positive case with valid
transactions, as invalid transactions don't propagate through the
network), there's no need for strictness annotations on the error
constructors.

This change removes the bang patterns (!) from:
- AlonzoContextError
- BabbageContextError
- ConwayContextError
- DijkstraContextError
Remove `NoThunks` instances for predicate failures and `ContextError` types
`NoThunks` instances are used for memory leak detection during development,
but predicate failures should never be retained in the ledger state - they
are only used for validation results. Removing these instances reduces
code maintenance burden and instance derivation overhead.

This change removes `NoThunks` instances from:

- All predicate failure types across Shelley, Allegra, Alonzo, Babbage,
  Conway, and Dijkstra eras
- All predicate failures in cardano-protocol-tpraos
- All `ContextError` types (`AlonzoContextError`, `BabbageContextError`,
  `ConwayContextError`, `DijkstraContextError`)
- The `NoThunks (ContextError era)` constraint from the `EraPlutusContext` class
- The `NoThunks` deriving instance for `CollectError`
Remove `NoThunks` instances for predicate failures and `ContextError` types
`NoThunks` instances are used for memory leak detection during development,
but predicate failures should never be retained in the ledger state - they
are only used for validation results. Removing these instances reduces
code maintenance burden and instance derivation overhead.

This change removes `NoThunks` instances from:

- All predicate failure types across Shelley, Allegra, Alonzo, Babbage,
  Conway, and Dijkstra eras
- All predicate failures in cardano-protocol-tpraos
- All `ContextError` types (`AlonzoContextError`, `BabbageContextError`,
  `ConwayContextError`, `DijkstraContextError`)
- The `NoThunks (ContextError era)` constraint from the `EraPlutusContext` class
- The `NoThunks` deriving instance for `CollectError`