Skip to main content

One post tagged with "backend"

View All Tags

Switching to Cardano database incremental certification

· 2 min read
Mithril Team

Switching to Cardano database incremental certification​

A new incremental certification process has been introduced for the Cardano node internal database. This enhancement is part of ongoing efforts to improve the Mithril protocol and optimize Cardano node bootstrapping.

More information about the Cardano database certification is available at:

The Cardano node database v2 certification offers incremental verification and greater efficiency compared to the original method. It will progressively replace the current certification process for the Cardano node internal database.

To facilitate this transition, updates have been made to both the Mithril client CLI and the Mithril client library. These changes are designed to support the new incremental certification process and ensure a smooth user experience.

In particular, the cardano-db command in the Mithril client CLI has been updated to support the new incremental certification process and eventually a seamless switch to the new backend. A new --backend option has been added to the command, allowing users to specify the certification version:

  • --backend v1 uses the original Cardano node database certification (this remains the default)
  • --backend v2 enables the new incremental Cardano node database certification.

To support this transition, both certification versions will remain available during the migration period, allowing users to adapt at their own pace.

  • Distribution 2524:

    • Introduced the --backend parameter in the cardano-db command
    • The default backend is v1; the v2 backend is still considered unstable
    • No breaking changes in the client CLI
    • The v2 backend is accessible via the cardano_database_v2 function in the client library.

  • Distribution +1:

    • The v2 backend will be promoted to stable status but will remain optional
    • The v1 backend will continue to be the default.

  • Distribution +2:

    • The v2 backend will become the default
    • The v1 backend will be deprecated.

  • Distribution +3:

    • The v1 backend will be decommissioned and removed from the client CLI and library.

  • Distribution +4:

    • The v1 backend will be fully removed from the signer and aggregator.

If you have any questions or need assistance, contact the team on the Discord channel.