Skip to main content

86 posts tagged with "consensus"

View All Tags

Consensus Team Update

· 3 min read
Damian Nadales
Damian Nadales
Consensus Team Lead

High level summary​

  • Continued Leios prototype development (Treasury Funding Initiative 4: Ouroboros Leios Implementation):
    • Implemented a run-threadnet CLI that allows configuring, running, and observing simulated Cardano networks (#1883). This tool enables the team to quickly test multi-node setups locally, significantly speeding up the investigation of implementation issues.
    • Drafted a baseline design for the Leios fetch logic with bounded memory usage (ouroboros-leios#797, ouroboros-leios#811). The design addresses the challenge of efficiently fetching and managing large volumes of data in Leios while keeping resource usage within practical limits. Work continues in March with an exploration of alternative storage strategies to further improve performance.
  • Peras development:
    • Added state-machine tests for the Peras vote database, strengthening the guarantees around the correctness of the voting mechanism (#1809).
  • Node improvements (Treasury Funding Initiative 17: Maintenance and Support):
    • Updated the Node-to-Client protocol to version 23, unlocking new queries for wallets and other tools that interact with the node (#1860).
    • Made it easier for developers to target the current era when querying the node (#1919).
    • Improved observability of chain selection by exposing the reasons behind chain switches (#1898).
    • Integrated a ledger fix for a bug in the Plutus script context (#1914).
  • Repository and tooling (Treasury Funding Initiative 17: Maintenance and Support):
    • Unified all consensus packages into a single package, simplifying the dependency landscape for downstream projects (#1895, #1912).
    • Enhanced the snapshot converter tool with a daemon mode that watches for new ledger snapshots and automatically converts them, useful for node operators managing different storage backends (#1887).
    • Added developer documentation for inspecting a node's chain (#1913).
  • Testing and quality (Treasury Funding Initiative 17: Maintenance and Support):
    • Generalized Genesis tests to support any block type, paving the way for conformance testing with real Cardano blocks (#1879).
    • Added support for GHC 9.14 (#1902).
    • Internal cleanup of chain selection and ledger database code (#1880).

Consensus Team Update

· 2 min read
Damian Nadales
Damian Nadales
Consensus Team Lead

High level summary​

  • Continued work on Node 10.7 integration (Treasury Funding Initiative 17: Maintenance and Support):
    • Integrated network packages up to ouroboros-network-0.22.6 (#1819, #1865).
    • Integrated latest ledger changes (#1762).
    • Integrated kes-agent-1.1 (#1819) (Treasury Funding Initiative 9: KES Agent).
  • Node improvements (Treasury Funding Initiative 17: Maintenance and Support):
    • Improved mempool behavior for local clients:
      • Downgraded hard timeouts to soft timeouts, improving user experience for wallets and other local client integrations (#1856, #1857, #1858).
      • Made it easier for downstream tracers to scrutinize mempool rejection details (#1847).
      • Enhanced observability by exposing the reason for chain switches in the ChainSel tracer (#1826).
    • Added support for the new GetDRepDelegations ledger state query in NodeToClientV_23 (#1794).
    • Fixed an exception due to a mix-up of resources in the V2 LedgerDB (#1842).
    • Minor: code cleanup (#1854).
    • Added documentation for the Consensus-Ledger interaction (#1830).
  • Continued Leios prototype development (Treasury Funding Initiative 4: Ouroboros Leios Implementation, MS4.6):
    • Refactored to use EbHash instead of EbId for cleaner design (#1859).
    • Simplified to monomorphic types for more rapid iteration (#1846).
    • Implemented in-memory LeiosDb for ThreadNet tests (#1837).

Consensus Team Update

· One min read
Damian Nadales
Damian Nadales
Consensus Team Lead

High level summary​

  • Continued work on Node 10.7 integration and release (Treasury Funding Initiative 17: Maintenance and Support).
  • Added defensive programming logic to the mempool (#1831), backported it via a CHaP release for cardano-node 10.6.2 (#1216), and drafted corresponding EKG counters for the 10.6.2 release engineer to use (#6420) (Treasury Funding Initiative 17: Maintenance and Support).
  • Prototyped Leios EB (Endorsement Block) production, advancing the implementation of the Leios protocol (#690). Successfully forged EBs and integrated them with the proto-devnet, complete with Grafana dashboards (Treasury Funding Initiative 4: Ouroboros Leios Implementation, MS4.6).
  • Working on optimizations for the centralized TxSubmission logic (#1444) (Treasury Funding Initiative 17: Maintenance and Support).
  • Released kes-agent and kes-agent-crypto version 1.0 (Treasury Funding Initiative 9: KES Agent, MS9.7).

Consensus Team Update

· 2 min read
Damian Nadales
Damian Nadales
Consensus Team Lead

High level summary​

  • Completed the LSM work in Consensus. Remaining LSM work is just integration in API, CLI, and Node which will be done as part of Node 10.7. In particular we:
    • Made forkers more observable (#1773).
    • Updated the code to reject legacy snapshots (#1774).
    • Updated to latest LSM-trees (#1776), including dependency updates to allow older filepath (#804) and older unix (#805).
  • Fixed a deadlock in the V1LMDB mempool implementation (#1787, #1798).
  • Resolved a memory leak in benchmarks for the 10.6.1 release (#1802).
  • Prepared a 10.6.1 node with LSM-trees for preliminary deployment on a relay to gather performance measurements.
  • Successfully compiled an untested prototype of a node using different tables per block, preparatory work for LedgerHD planned for Node 10.8.
  • Modified cardano-testnet to support running with kes-agent.
  • Made progress on migrating Leios demos to ouroboros-leios, including traffic control support for network delay and bandwidth configuration in Leios experiments (#651). The remaining work involves making sure CI passes and incorporating review feedback.
  • Continued work on Node 10.7 integration.

Consensus Team Update

· One min read
Damian Nadales
Damian Nadales
Consensus Team Lead

High level summary​

  • Participated in the November 2025 incident response, providing analysis on potential intervention scenarios and tracking chain progression metrics.
  • Merged documentation of the Leios Protocol Burst attack threat model (ouroboros-leios#624), strengthening the protocol's security foundation ahead of load testing and mitigation strategy development.
  • Continued preparation for the Leios November demo, with significant progress on observability infrastructure using Grafana and Prometheus (#1766), and demo packaging to streamline deployment (#1759). Both tasks are expected to be completed by end of week.