Upgrade to Cardano `11.2`
Maintainers usually reply within 2 days
@jpraynaud is already working on this.
Since Oct 2, 2026.
Assessment
This issue has not been assessed yet.
Description
Why
Once the new version of the Cardano node has been released: 11.2.X. We need to update this dependency in all our code base and make sure that Mithril nodes are compatible with it.
What
Upgrade the Cardano node (and Cardano cli) to 11.2.X on Mithril networks infrastructure and devnet.
How
- Check if ledger state needs to be recomputed with new Cardano node
11.2.X- 🔥 Yes, ledger state re-computation is needed
- Update Cardano configurations in infra
-
preview -
preprod -
mainnet
-
- Adapt support for
11.2.X:- Adapt the devnet (if needed)
-
Adapt the snapshot converter tool (if needed) -
Adapt the infrastructure (if needed) -
Adapt the CI workflows (if needed) - Verify that LSM ledger state restored works
- Check if the latest stable version of the Mithril aggregator and signer are compatible with new Cardano node
11.2.X:- Signer
- Aggregator
- Switch to
11.2.Xas default:- Cleanup previous unsupported Cardano configurations in infra
- Update the Cardano node to
11.2.Xin the infrastructure - Update the Cardano node to
11.2.Xin the Docker images - Update the Cardano node to
11.2.Xin the documentation - Update the Cardano node version to
11.2.Xin CI manual/nightly workflows - Add new entry in the E2E test in the CI for
11.2.X - Update the Cardano node to
11.2.Xin thedevnet - Update the Cardano node to
11.2.Xin the E2E test - Update the
networks.jsonfiles - Update the 'Network configurations' page
-
testing-preview -
pre-release-preview -
release-preprod -
release-mainnet
-
- Update the Cardano node version to
11.2.Xin the GitHub environments-
testing-preview -
testing-2-preview -
pre-release-preview -
release-preprod -
release-mainnet
-
- Dominant language
- Rust
- Stars
- 155
- Forks
- 52
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 37
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from IntersectMBO/mithril
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
IntersectMBO/mithril#1605 · 2 comments ·
Maintainers usually reply within 2 days
-
spike :satellite:
Difficulty 5/5 Over a week Newbie friendliness 10/100
IntersectMBO/mithril#3701 ·
Maintainers usually reply within 2 days
-
Publish a DNSLink record of the immutable archives IPNS name in the Mithril networks DNS zonesPossibly taken @jpraynaud claimed this 2 days ago. Openfeature :rocket:
IntersectMBO/mithril#3700 · 1 assignee ·
Maintainers usually reply within 2 days
-
feature :rocket:
Difficulty 4/5 3-5 days Newbie friendliness 25/100
IntersectMBO/mithril#3699 ·
Maintainers usually reply within 2 days
-
feature :rocket:
Difficulty 4/5 3-5 days Newbie friendliness 35/100
IntersectMBO/mithril#3698 ·
Maintainers usually reply within 2 days
All issues in IntersectMBO/mithril
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
storytold/photocraft#14822 ·
Maintainers usually reply within 1 day
-
bug css
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
dginev/latexml-oxide#853 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 2 days
-
[Bug] export_build_environment admits its output directory only after the export ran in the build computerPossibly taken @viniciusdsandrade claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day