Mithril v2423.0-pre

Highlights:

• 🔥 BREAKING changes in Mithril client CLI:
  • The deprecated snapshot command has been removed.
  • It has been superseded by the cardano-db command.
• Bug fixes and optimizations.

What's Changed

• Sign Cardano Transactions with Block Range Merkle Roots by @jpraynaud in #1660
• Prove Cardano Transactions with Block Range Merkle Roots by @jpraynaud in #1663
• Adding Mithril networks configuration to networks.json by @dlachaume in #1664
• Add new mithril logo and give credit by @ch1bo in #1665
• Ord on signed entity type discriminants by @Alenar in #1669
• Add benchmark tests for storing Cardano transactions by @dlachaume in #1666
• Upgrade project dependencies by @dlachaume in #1671
• Prune history of gh-pages branch by @ch1bo in #1670
• Rotate current documentation by @dlachaume in #1659
• Update CHANGELOG with 2418.1 distribution release by @jpraynaud in #1675
• Consistent transactions sort by @Alenar in #1672
• Build and setup Squid in SPO guide by @jpraynaud in #1612
• Stabilize test removing most of the time dependency by @sfauvel in #1673
• Common Cardano transactions & Block range roots repository by @Alenar in #1678
• Activate debug log for signers in infra by @jpraynaud in #1682
• Fix aggregator stress test by @dlachaume in #1679
• Upgrade documentation website dependencies by @dlachaume in #1658
• Fix squid service configuration in signer guide for SPO by @jpraynaud in #1684
• Support Cardano 8.11.0-pre in testing-sanchonet by @jpraynaud in #1696
• Prune cardano transactions in signer after block range roots computation by @Alenar in #1685
• feat: add get_current_chain_point function to fetch chain point information by @falcucci in #1674
• Fix Cardano transaction signed entity type timeout by @jpraynaud in #1702
• Create a test Cardano transactions builder by @dlachaume in #1703
• Add Mithril Protocol Insights dashboard link on website by @jpraynaud in #1706
• Add missing Genesis Verification Key for testing-mainnet by @jpraynaud in #1708
• Explorer in out registrations by @Alenar in #1709
• Fix Bootstrap a Cardano node guide by @jpraynaud in #1712
• Remove snapshot command by @sfauvel in #1710
• Update network compatibility table for releases by @jpraynaud in #1714
• Implement chainsync ChainReader with pallas by @jpraynaud in #1680
• Update BlockStreamer return type by @dlachaume in #1716
• Remove connection from database provider by @Alenar in #1715
• Add chain_point to TimePoint structure by @Alenar in #1717
• Add Block Range Merkle Map cache pool in Cardano Transactions prover by @jpraynaud in #1713
• Benchmark aggregator prover tool by @jpraynaud in #1718
• Make Cardano transaction prover able to certify more than 5 transactions by @jpraynaud in #1723
• Block Number beacon in cardano transaction by @Alenar in #1727
• Upgrade dependencies by @dlachaume in #1731

Full Changelog: 2418.1...2423.0-pre

Crates Versions

Crate	Version
mithril-aggregator	0.5.16
mithril-client	0.8.3
mithril-client-cli	0.9.2
mithril-client-wasm	0.3.3
mithril-common	0.4.13
mithril-signer	0.2.141
mithril-stm	0.3.22

Networks Compatibility ⚠️

Network	Compatible
release-mainnet	⛔
release-preprod	⛔
pre-release-preview	✔
testing-preview	⛔
testing-sanchonet	⛔

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 <[email protected]>" 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 <[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 ⚠️