Mithril v2321.1

What's Changed

• Make doc ci reports & fail if there's an error by @Alenar in #890
• add signable builder in signer by @ghubertpalo in #891
• Make Artifact usable as trait object by @jpraynaud in #889
• Mithril Stake Distribution Signable builder by @jpraynaud in #885
• Cardano Immutable Files Full Artifact builder in aggregator by @jpraynaud in #900
• Use Signable Builder Service in aggregator by @jpraynaud in #901
• Use Signable Builder Service in signer by @jpraynaud in #903
• Use Artifact Builder Service in aggregator by @jpraynaud in #906
• Handle multiple Signed Entity Types in aggregator/signer runtimes by @jpraynaud in #908
• Update dependencies by @jpraynaud in #923
• Implement new Stake Distribution computation by @jpraynaud in #921
• Implement Artifact routes by @jpraynaud in #924
• Fix legacy snapshot routes redirect by @jpraynaud in #926
• Add mithril stake distribution to explorer by @Alenar in #928
• Fix stake distribution computation for zero stake pools by @jpraynaud in #931
• rename signed entity service by @ghubertpalo in #929
• Update state machines runtime in Aggregator/Signer by @jpraynaud in #934
• Upgrade Cardano node to 8.0.0 by @jpraynaud in #922
• Fix open api version by @jpraynaud in #937

Full Changelog: 2318.0...2321.1

Crates Versions

Crate	Version
mithril-aggregator	0.3.23
mithril-client	0.2.22
mithril-common	0.2.56
mithril-signer	0.2.46
mithril-stm	0.2.13

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 <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 ./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 <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 ⚠️