Prepare Mithril for Cardano Dijkstra hard fork

未关闭
  • 哪里不对？
#3,673 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
8/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
blockchain, testing-qa

调研方向

This is a multi-phase epic, not a single change, so start by picking one sub-task and confirming scope with maintainers. The payload names the Pallas Rust dependency, the Mithril devnet, the CI end-to-end test suite, and a SanchoNet test network, but no specific files or entry points. Done means Mithril parses and certifies blocks across the new era boundary in those environments before mainnet activation.

由索引模型根据 Issue 内容生成。

描述

roadmap :compass:

Why

Cardano hard forks introduce modifications to the block and transaction structure that directly impact Mithril. Mithril nodes parse and certify Cardano chain data including blocks and transactions for Cardano Transactions certification using the Pallas library as the Cardano mini-protocol and data structure implementation. When a hard fork changes the on-chain data format, Mithril must be updated before the hard fork activates on mainnet, or it will fail to parse the new era's blocks and produce invalid or no certifications.

Getting Mithril ready for a hard fork requires several coordinated steps:

  • Upgrade Pallas to a version supporting the new era: Pallas must be updated to parse the new block and transaction structures. This is typically an iterative process across multiple Pallas pre-release versions as the new era's specification stabilizes, requiring repeated dependency bumps and adaptation to breaking API changes.
  • Adapt the devnet to support the new Cardano era: The Mithril devnet (a private test network used for local development) must be configured to trigger the hard fork so that developers can test Mithril nodes against the new era locally before any public testnet is available.
  • Implement the hard fork in the end-to-end tests: The CI end-to-end test suite must exercise the hard fork transition to verify that all Mithril nodes (aggregator, signer, client) remain compatible across the era boundary, catching regressions automatically.
  • Deploy a dedicated Mithril test network on SanchoNet (or equivalent): A Mithril network running on Cardano's hard fork testing network provides a realistic environment to validate the full certification pipeline (signing, aggregation, snapshot creation, client verification) under real hard fork conditions with actual Cardano nodes, before the hard fork reaches mainnet.
  • Fix bugs discovered during the adaptation phase: Each of the above steps will likely surface compatibility issues (parsing failures on new block formats, transaction certification mismatches, protocol message computation divergences between signers) that must be diagnosed and fixed iteratively.

This work must be completed and validated before the hard fork activates on mainnet. Any gap in readiness means Mithril stops producing valid certifications at the hard fork boundary, disrupting all clients relying on Mithril-certified Cardano data.

主要语言
Rust
星标
155
派生
52
平均合并
2 天 17 小时
30 天内合并 PR
37

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

IntersectMBO/mithril 的其他 Issue

查看 IntersectMBO/mithril 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。