Skip to content

Mithril v2408.0

Compare
Choose a tag to compare
@github-actions github-actions released this 26 Feb 13:46
· 685 commits to main since this release
5afc6fc

Highlights

  • ⚠️ Breaking change introduced in the Mithril client CLI: the logs output are switched from stdout to stderr from version 0.7.0.
  • Support for stake distribution and Mithril era markers retrieval in the Pallas chain observer in signer and aggregator.
  • Enhanced support for Conway era and Sanchonet network.
  • Bug fixes and performance improvements.

What's Changed

  • Fix npm authentication to registry in CI by @jpraynaud in #1448
  • Fix mithril-client wasm basic JS code example by @dlachaumepalo in #1449
  • Specify explicitly permissions for prerelease creation by @Alenar in #1452
  • Rotate current documentation by @dlachaumepalo in #1446
  • Increment mithril-client-wasm version for npm publish by @dlachaumepalo in #1453
  • Add dev blog post to announce Mithril client npm package by @jpraynaud in #1454
  • Gather and store Cardano transactions from immutable files by @jpraynaud in #1451
  • Fix npm badge in mithril-client-wasm README files by @dlachaumepalo in #1458
  • Compute message to sign for Cardano transactions by @jpraynaud in #1455
  • Fix missing test data in nix flake build by @jpraynaud in #1461
  • Enhance end to end test for Cardano hard forks by @jpraynaud in #1459
  • Fix building mithril-common with some features and targets combinatory by @Alenar in #1463
  • Failed end to end tests artifact names by @jpraynaud in #1472
  • List immutables resilience by @Alenar in #1465
  • Implement CardanoTransactions proof generation route in aggregator by @jpraynaud in #1473
  • Add mithril-client-wasm tests in multi platform test by @dlachaumepalo in #1462
  • Clean www/ directory by @dlachaumepalo in #1477
  • Update dependencies by @Alenar in #1476
  • Implement CardanoTransactions artifact routes in aggregator by @jpraynaud in #1479
  • Certificate hash in transaction set message by @Alenar in #1485
  • More explicit error message when db dir is not writable by @abailly-iohk in #1483
  • Remove http from dependencies by @Alenar in #1490
  • Support Sanchonet Cardano network by @jpraynaud in #1384
  • Add Cardano transactions proofs support to mithril-client by @Alenar in #1489
  • Fix clippy lint from rust 1.76 by @Alenar in #1493
  • Sfa/improve signed entity test by @sfauvel in #1460
  • Add dev blog post announcing testing-sanchonet network by @jpraynaud in #1491
  • Minor adjustments to generic identifier descriptions by @olgahryniuk in #1498
  • Extract persistence related code to a new shared crate by @Alenar in #1494
  • get datums using pallas observer by @falcucci in #1403
  • Cardano transaction sets & proof in client cli by @Alenar in #1501
  • Update Mithril architecture documentation by @jpraynaud in #1499
  • Fix clippy warning in common when using only fs flag by @Alenar in #1504
  • Upgrade Cardano configurations in infra by @jpraynaud in #1505
  • Add signing capabilities to aggregator root route by @dlachaumepalo in #1506
  • Update SPO-on-boarding-guide.md, it's not required (anymore?) to run … by @brouwerQ in #1507
  • Add example crate for Cardano transactions by @dlachaumepalo in #1511
  • Generate documentation on module command lines by @sfauvel in #1424
  • Implement Cardano transactions verification in mithril-client-wasm by @dlachaumepalo in #1512
  • Mithril client CLI: fix remove archive directory by @dlachaumepalo in #1517
  • Enhance client-cli standard output by @Alenar in #1516
  • add pallas stake snapshots integration by @falcucci in #1513
  • CI: Upgrade actions by @Alenar in #1521
  • Fix update_release action version in CI by @Alenar in #1525
  • Upgrade mithril-client-wasm minor version to 0.2.0 by @dlachaumepalo in #1526

New Contributors

Full Changelog: 2403.1...2408.0

Crates Versions

Crate Version
mithril-aggregator 0.4.39
mithril-client 0.6.4
mithril-client-cli 0.7.0
mithril-client-wasm 0.2.0
mithril-common 0.3.7
mithril-signer 0.2.109
mithril-stm 0.3.15

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