Mithril v2313.0-prerelease

What's Changed

• Update Era Switch documentation by @jpraynaud in #790
• Fix Docker Client crash by @jpraynaud in #792
• Fix clippy warnings from Rust 1.68.0 by @jpraynaud in #795
• Update dependencies by @jpraynaud in #796
• Update dev blog post Era Switch by @jpraynaud in #797
• add stake_pool provider by @ghubertpalo in #789
• Upgrade VM testing-preview & pre-release-preview networks by @jpraynaud in #802
• Update Mithril Client multi-platform test workflow by @jpraynaud in #793
• Avoid compute stake distribution multiple times per epoch by @jpraynaud in #805
• Add aggregator 'genesis' command doc by @jpraynaud in #806
• Update KES by @iquerejeta in #783
• Greg/799/pruning by @ghubertpalo in #808
• Greg/799/refactor sqlite connection by @ghubertpalo in #809
• Fix devnet Genesis Alonzo URL by @jpraynaud in #819
• Handle API version with Era Switch by @jpraynaud in #812
• Clean Genesis Verification Key by @jpraynaud in #821
• #799 stake pool service by @ghubertpalo in #800
• Enhance Key Registration errors by @jpraynaud in #822
• Update dependencies by @jpraynaud in #830
• Update Rust dependencies by @jpraynaud in #832
• Cleanup multi-signer by @jpraynaud in #825
• Fix mislabeled critical error by @jpraynaud in #833

Full Changelog: 2310.0...2313.0-prerelease

Crates Versions

Crate	Version
mithril-aggregator	0.2.38
mithril-client	0.2.14
mithril-common	0.2.33
mithril-signer	0.2.28
mithril-stm	0.2.9

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 gpg-public.key and save it in the same folder as the asset
• Step 6: Then import the GPG public key:

gpg --import ./gpg-public.key

You must see something like:

gpg: key : public key "Input Output / Mithril <[email protected]>" imported
gpg: Total number processed: 1
gpg:               imported: 1

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

gpg --verify ./gpg-public.key ./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 <[email protected]>" [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 <[email protected]>"
• 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 [[email protected]] and let us know of the outcome of your run of this process ⚠️