Mithril v2347.0

Highlights

• Public release of the Mithril client library available for developers on crates.io.
• Support for slim certificates produced by the Mithril aggregator ⁽¹⁾.
• Bug fixes and performance improvements.

⁽¹⁾: requires Mithril client (a.k.a mithril-client-cli) 0.5.5+ for restoration ⚠️.

What's Changed

• Aggregator keyreg bottleneck by @Alenar in #1295
• Update current documentation by @jpraynaud in #1307
• Add missing configuration parameters in signer documentation by @jpraynaud in #1317
• Explorer certificates list & signers summary by @Alenar in #1309
• rework client to export mithril API by @ghubertpalo in #1291
• Handle sqlite access using a ConnectionWithFullMutex by @Alenar in #1316
• total_stake calculation corrected by @curiecrypt in #1308
• Fix aggregator HTTP server CORS by @jpraynaud in #1318
• add soft limit in certificate query by @ghubertpalo in #1314
• Simplify certificate verifier usage by @Alenar in #1319
• Rename mithril-client to mithril-client-cli by @Alenar in #1320
• Client regressions in snapshot list and download by @dlachaumepalo in #1323
• Enhance Mithril nodes devnet Docker images by @jpraynaud in #1324
• Fix devnet crashing at startup by @jpraynaud in #1329
• Fix client CLI Docker package name in CI/CD by @jpraynaud in #1330
• Revert "add soft limit in certificate query" by @ghubertpalo in #1328
• Add Mithril end to end instructions for --skip-cardano-bin-download command by @dlachaumepalo in #1331
• Greg/1310/lower serialization by @ghubertpalo in #1333
• Fix certificate chain hashes recomputation by @jpraynaud in #1337
• Enhance end to end readme and fix work_directory default value on MacOS by @dlachaumepalo in #1338
• Add SSH key by @dlachaumepalo in #1339
• Add linebreak after last ssh key by @dlachaumepalo in #1340
• Redesign mithril client api by @Alenar in #1332
• Add subnote and git command for unstable release by @dlachaumepalo in #1334
• Fix github action contains expression by @dlachaumepalo in #1342
• Simplify common deps by @Alenar in #1341
• Fix certificate hashes re-computation in aggregator by @jpraynaud in #1345
• enhance Aggregator REST API performances by @ghubertpalo in #1347
• Mithril client and common crates preparation for publication by @jpraynaud in #1349
• Upgrade dependencies by @jpraynaud in #1351
• Mithril relay P2P network for signatures PoC by @jpraynaud in #1346
• Use Cardano node custom version CI/CD by @jpraynaud in #1359
• Manual deployment of test Mithril network by @jpraynaud in #1358
• Runbooks for test distributions and deployments by @jpraynaud in #1360
• HTTP message service by @ghubertpalo in #1353
• Mithril-client-lib: Gate snapshot download & message computation behind a feature by @Alenar in #1344
• Fix Mithril relay Rust doc by @jpraynaud in #1364
• Standardize default environment file path of Signer node configuration for SPOs by @dlachaumepalo in #1365

Full Changelog: 2342.0...2347.0

Crates Versions

Crate	Version
mithril-aggregator	0.4.12
mithril-client	0.5.7
mithril-client-cli	0.5.5
mithril-common	0.2.135
mithril-signer	0.2.90
mithril-stm	0.3.10

Networks Compatibility ⚠️

Network	Compatible
release-mainnet	✔
release-preprod	✔
pre-release-preview	✔
testing-preview	✔

Linux Requirements

The Linux binaries target glibc: to run them or install the .deb packages you must have glibc version 2.31+ installed.
Compatible systems include, but are not limited to, Ubuntu 20.04+ or Debian 11+ (Bullseye)).

Verify the authenticity of a downloaded asset

Detailed procedure to verify an asset

• Step 1: Identify the downloaded asset on your computer YOUR_ASSET_FILE
• Step 2: Download the signed checksum file from this link CHECKSUM.asc and save it in the same folder as the asset
• Step 3: In your terminal, go to the asset folder by running:

cd ***YOUR_ASSET_FOLDER***

• Step 4: Then verify the checksum of the asset by running:

sha256sum -c ./CHECKSUM.asc 2>/dev/null | grep ***YOUR_ASSET_FILE***

You must see:

./***YOUR_ASSET_FILE***: OK

• Step 5: Download the public key file from this link public-key.gpg and save it in the same folder as the asset
• Step 6: Then import the GPG public key:

gpg --import ./public-key.gpg

You must see something like:

gpg: key : public key "Input Output / Mithril <mithril@iohk.io>" imported
gpg: Total number processed: 1
gpg:               imported: 1

• Step 7: Then verify the GPG signature of the checksum file:

gpg --verify ./public-key.gpg ./CHECKSUM.asc

You must see something like:

gpg: Signature made Mon 05 Dec 2022 04:53:54 PM CET
gpg:                using RSA key 35EDE9D47BBA62A2F388E655899ACD26B8BCA0D2
gpg: Good signature from "Input Output / Mithril <mithril@iohk.io>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 35ED E9D4 7BBA 62A2 F388  E655 899A CD26 B8BC A0D2

The signature is valid if and only if:

• there is a line with gpg: Good signature from "Input Output / Mithril <mithril@iohk.io>"
• there is a line with Primary key fingerprint: 2AC0 7B11 8B23 1443 F544 2D0C 6E2C 1160 3E79 0021

• Step 8:
  If you successfully validated all the steps of this process, then you have successfully verified the authenticity of the asset ✔️
  If not, contact us at [mithril@iohk.io] and let us know of the outcome of your run of this process ⚠️