Prepare Mithril for Cardano Dijkstra hard fork

Abierto
  • ¿Algo no está bien?
#3,673 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
blockchain, testing-qa

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Rust
Estrellas
155
Forks
52
Merge medio
2 d 17 h
PR fusionados (30 d)
37

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de IntersectMBO/mithril

Todos los issues de IntersectMBO/mithril

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.