Skip to main content

67 posts tagged with "consensus"

View All Tags

· One min read
Damian Nadales

High level summary​

  • Updated the centralized chain-sync-jumping model to allow using it as a substitute for the real model, which will make it easier to troubleshot potential test failures found in our property tests (#1466).
  • Engaged with Cardano Foundation on the Antithesis workstream, which will help us widen the test coverage and robustness of the Cardano node.
  • Enriched db-immutaliser to inspect a VolatileDB (1482).
  • Released Node 10.4.1, which incorporates the UTXO-HD feature. The default backend will be the in memory one. The LMDB backed is not recommended for block producers, but we encourage users to experiment with it and report their experience.
    • Our benchmarks show no significant performance degradation, rating it production ready.
      • A small 2% / 5% (169MiB / 389MiB) increase in heap size could be expected.
      • However, this is mitigated by the fact that going from 10.2 to 10.3, we saw a significant reduction in heap size - namely 6% / 14% (579MiB / 1267MiB).
      • 10.4 reduces CPU usage slightly again
      • There is no impact on network performance.

· One min read
Damian Nadales

High level summary​

  • Work is ongoing on improving the Genesis tests. In particular, a centralized chain-sync-jumping model was developed to help troubleshoot test failures, which proved difficult to do using the decentralized model.
  • The Consensus team had its representative in the Node Diversity workshop. The report can be found in this link.
  • Collaborated with the Ouroboros Phalanx/Anti-Grinding Innovation Team, as an initial step in providing engineer input on the design.

· 2 min read
Damian Nadales

High level summary​

  • Well-Typed has presented the penultimate milestone for the lsm-tree library. Table unions are now fully supported, tests include IO-error injection, and compatibility across Linux, Windows, and macOS has been demonstrated.
    • The next milestone will finalize the library's development, enabling its integration as a persistent backend for storing ledger state.
  • Several Consensus team members attended the Peras workshop. There is a brief presentation that can be accessed by following this link (password is GDdL*6M%). A design and implementation plan has been drafted. The next steps for Peras involve a decision by relevant stakeholders (Intersect Technical Steering Committee, involving SPOs and users) regarding the tradeoffs inherent to the protocol, such as additional operational costs, rewards and protocol parameterization regarding settlement times.
  • We held our technical working group meeting (recording), where we discussed:
    • The possibility of incorporating batch VRF support into ouroboros-consensus.
    • CDDL definition for Consensus: draft PR and next steps.
    • Should we support for NTC for older eras? (#1429).
  • Exposed a function that asks Consensus for the versions in which a particular query is supported, offloading this logic from cardano-api (#1437).
  • Exposed Byron cddls to be used from Consensus (#4965).
  • Added QueryStakePoolDefaultVote for 10.3 ([#1434](https://github.com/IntersectMBO/ouroboros-consensus/pull/1434 release consensus for node 10.3)).

· One min read
Damian Nadales

High level summary​

  • Added a significant amount of content to the Consensus blueprint documentation. There are new sections that describe different aspects of the Consensus layer (such as chain selection or ledger queries), Storage layer, and Mempool.
  • Javier and Nick, two of the Consensus team members participated in the Cardano Dev Pulse Podcast where they discussed UTXO-HD and Genesis.