Mithril v2342.0-pre

Highlights

• Support for SPO tickers displayed next to their pool Ids in the Mithril explorer.
• Support for producing slim Docker images for the Mithril nodes.
• Bug fixes and performance improvements.

What's Changed

• Implement anyhow context in aggregator runtime by @dlachaumepalo in #1240
• Implement anyhow context in aggregator/services by @dlachaumepalo in #1242
• Implement anyhow context in aggregator/signer_register by @dlachaumepalo in #1243
• Implement anyhow context in aggregator/snapshotter by @dlachaumepalo in #1246
• refactored aggregator client errors by @ghubertpalo in #1245
• refactored client configuration errors by @ghubertpalo in #1248
• Use anyhow in aggregator multi-signer by @jpraynaud in #1247
• refactor common sqlite errors by @ghubertpalo in #1249
• Add anyhow context mithril-client/aggregator-client by @dlachaumepalo in #1250
• Add anyhow context in mithril-client/commands by @dlachaumepalo in #1252
• Add anyhow context in mithril-client/dependencies by @dlachaumepalo in #1253
• Fix aggregator stress test bottleneck with client traffic by @jpraynaud in #1251
• Use anyhow in signer single-signer by @jpraynaud in #1255
• Update current documentation by @jpraynaud in #1258
• Fix terraform composite action by @jpraynaud in #1259
• Add anyhow context for mithril-client/services by @dlachaumepalo in #1256
• remove store error by @ghubertpalo in #1257
• Fix explorer display units by @jpraynaud in #1261
• Get rid of string error comparison in tests by @dlachaumepalo in #1260
• Add errors standards ADR by @jpraynaud in #1266
• Add anyhow in integration & e2e tests by @Alenar in #1264
• Enhance signer setup guide for SPO by @jpraynaud in #1263
• Use source attribute in wrapped errors by @Alenar in #1268
• Add a JSON message response on /aggregator endpoint calls by @dlachaumepalo in #1270
• Benchmark aggregator performances by @jpraynaud in #1271
• Upgrade dependencies by @jpraynaud in #1275
• Add Mithril networks status page in website footer by @jpraynaud in #1278
• Add signers ticker automatic import process + /signers/tickers route to aggregator http server by @Alenar in #1276
• Deploy infrastructure for SPO tickers by @jpraynaud in #1279
• Update flake.lock by @yvan-sraka in #1281
• SPO tickers in explorer by @Alenar in #1280
• Upgrade Rust 1.73.0 by @jpraynaud in #1285
• Cache /signers/tickers calls in explorer by @Alenar in #1286
• Prettier formatter for explorer by @Alenar in #1288
• Upgrade dependencies by @dlachaumepalo in #1289
• Fix mithril-stm WASM build by @jpraynaud in #1290
• Infrastructure VM upgrade runbook by @jpraynaud in #1293
• Rename GPG public key in releases by @jpraynaud in #1294
• Mithril relay security advisory dev blog post by @jpraynaud in #1296
• Fix missing aggregator configuration in devnet by @jpraynaud in #1297
• Fix typo in relay security advisory dev blog post by @jpraynaud in #1301
• Publish multiple packages to crates.io by @jpraynaud in #1299
• Upgrade dependencies by @jpraynaud in #1304
• Update contributing guidelines by @jpraynaud in #1305
• Refactor Dockerfile.ci to slim containers by @TrevorBenson in #1302

New Contributors

• @TrevorBenson made their first contribution in #1302

Full Changelog: 2337.0...2342.0-pre

Crates Versions

Crate	Version
mithril-aggregator	0.3.111
mithril-client	0.4.12
mithril-common	0.2.126
mithril-signer	0.2.87
mithril-stm	0.3.8

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