Skip to main content

· 3 min read
Alexey Kuleshevich

High level summary​

Ledger team has successfully defined what sub-transaction really means for Nested Transactions in Dijkstra era. We've also reduced quite a bit of duplication with respect to how CDDL is specified with further improvements that are still in progress. We have fixed some serialization issues for Dijkstra era that we couldn't fix for previous eras, which had to do with preventing duplicates being supplied over the wire. Besides these improvements we've also cleaned up some deprecated functionality, reduced memory overhead in ledger state, improved performance of the epoch boundary transition and fixed some issues in conformance tests.

Low level summary​

Features​

  • PR-5361 - Disable old redeemer deserialization
  • PR-5316 - Store delegators in pool state
  • PR-5375 - More CDDL de-duplication
  • PR-5376 - Remove all deprecated functionality introduced before the latest release
  • PR-5384 - Remove Generic instance from BoundedRatio type
  • PR-5382 - Even more CDDL
  • PR-5391 - Store future pools in PState as StakePoolParams
  • PR-5396 - Replace okeyL method with toOKey
  • PR-5386 - Add a subtransactions field to DijkstraTxBodyRaw
  • PR-5402 - Add custom Show instance for the Mismatch type, to show the Relation between the values
  • PR-5398 - Intern stake credentials in reverse delegations
  • PR-5411 - Switch to using TypeData extension
  • PR-5394 - CDDL: Consolidate certificates and pool params
  • PR-5417 - Fix Monoid instance for VMap
  • PR-5397 - Limit protocol version to Word32 from version 12
  • PR-5373 - Make decoders fail when encountering duplicate elements in TxWits
  • PR-5430 - Reflect subtransactions in dijkstra CDDL

Testing​

  • PR-5347 - Move or replace BabbageFeatures tests in cardano-ledger-test
  • PR-5385 - Fix stakepool-test in nightly build
  • PR-5184 - Write an ImpTest to reproduce #5170
  • PR-5370 - Add a golden test for duplicate certificates
  • PR-5406 - Update fls and enable test
  • PR-5415 - Run the specification rules of EPOCH and NEWEPOCH in conformance tests
  • PR-5423 - Clean cardano-ledger-conformance
  • PR-5428 - Update formal-ledger-specifications

Infrastructure and releasing​

  • PR-5410 - Use ghc 9.10 for Haddocks in GH Pages CI
  • PR-5422 - Add support for nothunks == 0.3.*
  • PR-5348 - Update SECURITY.md
  • PR-5425 - Upgrade the version of Ruby used in GH CI to match the nix flake

· 2 min read
Jean-Philippe Raynaud

High level overview​

This week, the Mithril team completed the first phase of decentralizing configuration parameters and made good progress on implementing a simple aggregator discovery mechanism. Additionally, they kept working on the SNARK-friendly STM library by designing its architecture, implementing the Schnorr signature scheme, refactoring error handling, and experimenting with a Jubjub curve implementation in the BLST library.

Finally, they fixed some bugs, made enhancements to the CI, and continued improving the protocol security page.

Low level overview​

Features​

  • Completed the issue Decentralization of configuration parameters - Phase 1 #2692
  • Worked on the issue Implement a simple aggregator discovery mechanism #2726
  • Worked on the issue Architecture of the SNARK-friendly STM library #2763
  • Worked on the issue Implement Schnorr signature scheme in STM #2756
  • Worked on the issue Refactor error handling in STM library #2764
  • Worked on the issue Experimental blst-Jubjub #2772
  • Worked on the issue Test Haskell DMQ node message authentication (KES signature) #2786

Protocol maintenance​

  • Completed the issue Refactor AggregatorClient trait in signer #2759
  • Completed the issue Add fast bootstrap of Cardano node with LMDB UTxO-HD verification in CI #2679
  • Completed the issue Some tests fail in CI due to no space left on GitHub runners #2782
  • Worked on the issue Support optional cardano_transactions_signing_config #2780
  • Worked on the issue Enhance protocol security page on website #2703

· One min read
Ziyang Liu

High level summary​

The Plutus team is finalizing work for the upcoming intra-era hard fork.

Four of the Value primitives have now been costed, and the remaining three are currently in progress. After this, the final step before will be performing end-to-end testing for all new features to be introduced in the hard fork.

We are also preparing a blog post on UPLC 2025, which will be published soon.

In parallel, we continue progressing on other tasks, including support case analysis related to Data.

Low level summary​

Key Pull Requests Merged​

Issues and Pull Requests In Progress​

  • End-to-end testing for dropList
  • End-to-end testing for modular exponentiation
  • End-to-end testing for multi-scalar multiplication
  • End-to-end testing for Array primitives
  • End-to-end testing for Value primitives
  • End-to-end testing for unification of primitives across Plutus V1, V2 and V3

· One min read
Noon van der Silk

What did the team achieve?​

  • Great progress on partial fanout #1468
  • Improved logging for failed HTTP requests #2315
  • Added API to get head opened time #2316
  • Worked on a new "SafeClose" client input to try and avoid closing when you have unburned minted tokens #2330
  • Progress on making sure hydra is in sync with the chain #2286
  • Linked the new VTech Hydra SDK!

What's next?​

  • Finsh off work on "SafeClose" feature #2330
  • Build a demo using the VTech SDK #2353
  • Continue working on partial fanout #1468
  • Continue working on chain following approach #2206

· One min read
Damian Nadales

High level summary​

  • Discovered the "bufferbloat" pathology of the October 2025 Leios demo. Opened #1756 to troubleshoot it.
  • Introduced additional changes needed for LSM-tree integration in cardano-node (#1715).
  • Fixed race conditions and double read-lock acquisitions in the LedgerDb, and improved resource management in the LedgerDb (#1737, #1741).
  • Improved memory management by preventing the retention of the Genesis ledger state, which is particularly relevant during benchmarking and testing (#1731).
  • Improved resource management in the mempool and LedgerDb (#1714).