3 posts tagged with "cardano"

Announcing the decommissioning of the testing‑sanchonet network​

The testing-sanchonet Mithril network was introduced a year ago to allow the community to test experimental features and provide feedback to the Mithril team. In particular, it has been a valuable tool for testing the transition to the Conway era.

The Mithril team sincerely appreciates the Mithril pioneer stake pool operators for participating in testing and providing valuable feedback!

The Cardano SanchoNet network is now being sunset, having served its purpose of introducing governance features from CIP-1694 in a controlled testnet environment.

In this context, the Mithril team has decided to decommission the testing-sanchonet network:

• the aggregator will be terminated by February 21, 2025
• the network will be removed from the Mithril explorer
• the repository code will be cleaned up.

If you are running a Mithril signer on this network, you can safely terminate your node and remove the testing-sanchonet configuration from your setup.

Available Mithril networks are listed on the Network configurations page of the documentation website.

For any inquiries or assistance, contact the team on the Discord channel.

The release of the Mithril SanchoNet testing network​

The Mithril team has released the new testing-sanchonet Mithril network.

Mithril pioneer stake pool operators (SPOs) are welcome to run a Mithril signer on this network, with configuration parameters available here.

It's important to note that this network will serve as the primary platform for experimenting with unstable features of the Mithril networks in the future, such as the Cardano transactions set signatures or peer-to-peer (P2P) networking.

The unstable features are consistently developed and deployed to the SanchoNet testing network directly from the main branch of the Mithril repository. Therefore, Mithril nodes operating on this network must be either built from the main branch or use pre-built binaries from the unstable release. Failure to update Mithril nodes to the latest unstable version or encountering a bug during development could result in operational disruptions.

Note that the testing-sanchonet network undergoes continuous monitoring, and its availability status is reported on this status page.

For any inquiries or assistance, don't hesitate to reach out to the team on the Discord channel.

Update 2022/12/19: The signer registration with declarative PoolId has been decommissioned.

Update 2022/11/30: The signer registration with declarative PoolId has been deprecated and the certified PoolId is now the stable mode.

The way the Mithril nodes handle the Certification of the SPOs is evolving​

PR: New STM registration procedure #433

Issues: Implement Certification of the Mithril Verification Keys in Signer/Aggregator #455

We have released a new Mithril Signer Verification Keys Certification mechanism:

• Mithril Signer nodes running the previous version are still able to interact with the network without any further intervention
• Mithril Signer nodes that are updated from a previous version must migrate some of their stores
• This mechanism is experimental and can be activated on demand by the SPOs

Upgrade a Mithril Signer running a previous version​

The SPOs need to recompile their Signer node (as in this guide).

The data stores of the node need to be updated by running the following command:

# The path to your data stores directory, which defaults to:
DATA_STORES_DIRECTORY=/opt/mithril/stores

# Run this command to upgrade your stores:
sqlite3 ${DATA_STORES_DIRECTORY}/signer.sqlite3 "UPDATE protocol_initializer SET value = json_object('stm_initializer', json(value), 'kes_signature', null) WHERE json_extract(value, '$.stm_initializer') IS NULL;"

⚠️ If you don't update your data stores with this procedure, your node will not be able to register to the Aggregator temporarily. It should then take up to 3 epochs before it is able to successfully register its individual signatures with the Aggregator.

Hybrid Certification mode in the Mithril network​

From now, SPOs can either run their node by:

• Declaring their Cardano PoolId:

  • This is the mode that all nodes were running prior to this release
  • This mode is still the stable mode
  • We intend to deprecate this mode in the near future

• Certifying their Cardano PoolId:

  • The certification is done by providing the Mithril Signer node with KES Secret Key Path and Operational Certificate Path
  • This is an experimental mode
  • We intend to make this mode the only way of providing a PoolId in the near future
  • These PoolIds will be marked with a Verified Signer green badge in the Mithril Explorer (2 epochs after activating the Certification mode)

The setup of a Mithril Signer node with these two modes is available in this guide.

Here is an example of the Verified Signer badge displayed in the Certificate details popin:

How Keys Certification works​

We rely on the Cardano KES Keys and Operational Certificate to be able to:

• Compute automatically the PoolId from a valid Operational Certificate
• Sign the Mithril Signer Verification Key with the KES Secret Key
• Verify that the Mithril Signer Verification Key is associated to the owner of the pool

Feel free to reach out to us on the Discord channel for questions and/or help.