Mithril v2337.0

Highlights

• Support for zstandard compression algorithm for creating snapshot archives ⁽¹⁾.
• Support for Cardano node version used to create archive in the snapshot metadata.
• Support for recording download statistics in the aggregator.

⁽¹⁾: requires Mithril client 0.4.2+ for restoration ⚠️.

What's Changed

• Use zstandard compression for snapshot archives by @Alenar in #1195
• Fix Mithril network compatibility in unstable release by @jpraynaud in #1196
• Add anyhow context for api_version by @dlachaumepalo in #1201
• Implement anyhow context for beacon_provider by @dlachaumepalo in #1202
• Update current documentation for distribution 2335.0 by @jpraynaud in #1204
• Implement anyhow context for certificate chain by @dlachaumepalo in #1205
• Add Cardano Node version to the artifacts by @ghubertpalo in #1203
• Stress test aggregator phase 2 by @jpraynaud in #1194
• add database migration for snapshots by @ghubertpalo in #1209
• Add snapshot archive compression algorithm in explorer by @jpraynaud in #1210
• display cardano node version in client by @ghubertpalo in #1211
• Enhance aggregator stress tester performances by @jpraynaud in #1214
• Greg/947/cardano node version doc by @ghubertpalo in #1216
• compare for avk by @curiecrypt in #1217
• Implement anyhow context in mithril-common database by @dlachaumepalo in #1212
• Implement anyhow context for adapters by @dlachaumepalo in #1221
• Use anyhow in Era framework by @ghubertpalo in #1223
• refacto message parts by @ghubertpalo in #1225
• Use compression parameters in the terraform deployments by @jpraynaud in #1222
• Implement anyhow context in mithril-aggregator database by @dlachaumepalo in #1213
• Implement anyhow context for signable_builder by @dlachaumepalo in #1226
• Implement anyhow for common store by @dlachaumepalo in #1227
• Add aggregator CDN support in infrastructure by @jpraynaud in #1206
• Implement anyhow context for digesters by @dlachaumepalo in #1228
• Implement anyhow context for common/protocol by @dlachaumepalo in #1229
• Upgrade dependencies by @jpraynaud in #1231
• Implement anyhow context for artifact builder by @dlachaumepalo in #1232
• Use anyhow in common/crypto_helper by @jpraynaud in #1224
• Implement anyhow context for aggregator configuration by @dlachaumepalo in #1236
• Implement anyhow context: dependency_injection by @dlachaumepalo in #1237
• Upgrade client version to 0.4.0 by @jpraynaud in #1241
• Greg/1127/download statistics by @ghubertpalo in #1239
• Fix record download statistics by @jpraynaud in #1244

Full Changelog: 2335.0...2337.0

Crates Versions

Crate	Version
mithril-aggregator	0.3.95
mithril-client	0.4.2
mithril-common	0.2.115
mithril-signer	0.2.80
mithril-stm	0.3.3

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