Mithril v2318.0-prerelease

What's Changed

• Create/Migrate signer store by @jpraynaud in #861
• Update dependencies by @jpraynaud in #863
• Create/Migrate single_signature store by @jpraynaud in #864
• Implement Signable & Artifact Builders by @jpraynaud in #865
• Add flake.nix by @manveru in #811
• #850 Certifier service by @ghubertpalo in #866
• Add open message domain type by @Alenar in #879
• Fix Signer Registration Discrepancy by @jpraynaud in #877
• Implement Artifact Restorer by @jpraynaud in #875
• Update Cardano node to 1.35.7 by @jpraynaud in #882
• Update dependencies by @jpraynaud in #883
• Cleanup legacy single signature store by @jpraynaud in #884
• Mithril Stake Distribution Signable builder in aggregator by @jpraynaud in #867
• Greg/852/immutable signable by @ghubertpalo in #886
• Mithril Stake Distribution Artifact builder in aggregator by @jpraynaud in #887

New Contributors

• @manveru made their first contribution in #811

Full Changelog: 2315.0...2318.0-prerelease

Crates Versions

Crate	Version
mithril-aggregator	0.3.8
mithril-client	0.2.19
mithril-common	0.2.44
mithril-signer	0.2.36
mithril-stm	0.2.12

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