Mithril v2437.1
Highlights:
- 🔥 BREAKING changes in Mithril client WASM:
- Implementation of seamless transition from unstable to stable features.
- A new
unstable
option in the client allows the usage of unstable features. - The previous
client.unstable
implementation is not supported anymore and must be replaced withclient
.
- Stable support for Cardano transactions certification in signer and aggregator.
- Stable support for Cardano stake distribution certification in signer and aggregator.
- Bug fixes and performance improvements.
What's Changed
- Implement signable and artifact builders for Cardano Stake Distribution by @dlachaume in #1847
- Increase timeout for client WASM headless browser tests by @dlachaume in #1864
- Fix typos by @sfauvel in #1865
- Update CHANGELOG for
2430.0
distribution release by @jpraynaud in #1866 - Dev blog post for
Cardano transaction certification
feature roll-out by @jpraynaud in #1868 - Make signed_entity_type non optional in RegisterSignatureMessage by @sfauvel in #1870
- Monitor Mithril nodes footprint by @jpraynaud in #1871
- Add a redirection on index.html to clean url by @sfauvel in #1869
- Escape slashes in sed command by @sfauvel in #1873
- Update Mithril signer footprint with Cardano transactions by @jpraynaud in #1874
- Fix:
ChainReaderBlockStreamer
skipsRollForward
blocks at the tip by @jpraynaud in #1877 - Implement Cardano stake distribution HTTP routes by @dlachaume in #1872
- Update Mithril signer footprint in SPO guide by @jpraynaud in #1879
- Implement Cardano stake distribution in
mithril-client
library by @dlachaume in #1882 - Implement Cardano stake distribution commands in
mithril-client
CLI by @dlachaume in #1883 - Implement Cardano stake distribution in
mithril-client
WASM by @dlachaume in #1887 - Add new tab Cardano Stake Distribution in the explorer by @dlachaume in #1888
- Document Cardano Stake Distribution by @dlachaume in #1889
- Add missing Cardano stake distribution example in developer documentation by @dlachaume in #1891
- fix: macOS e2e local tests fails on M3 silicon processors by @falcucci in #1767
- Add support for custom HTTP Headers in Mithril client WASM library by @dlachaume in #1890
- Create repository dependencies upgrade runbook by @dlachaume in #1893
- feat: support
file://
URLs for snapshot locations by @michalrus in #1885 - Fix: Cardano stake distribution certification epoch discrepancy by @jpraynaud in #1896
- Optimize memory usage of signer for Cardano transactions by @jpraynaud in #1904
- Add Cardano transactions signing configuration in Aggregator '/' route by @Alenar in #1905
- Reorganize signer dependencies by @Alenar in #1908
- docs: update signer footprint in SPO setup guide by @jpraynaud in #1907
- Optional signed message in registered signatures by @Alenar in #1909
- feat: Make
rug-backend
optional formithril-client
crate by @Mr-Leshiy in #1884 - Chore: post
Chang
hard fork cleanup by @jpraynaud in #1912 - Refactor: seamless
unstable
tostable
transition in WASM client by @jpraynaud in #1914 - Fix clippy warnings from Rust 1.81 by @Alenar in #1918
- Add a script to update all dependencies by @sfauvel in #1916
- Feat: add infinite Cardano transactions preloader in signer by @jpraynaud in #1921
- Update dependencies for release 2437 by @Alenar in #1919
- Enhance upgrade dependency runbook by @Alenar in #1926
- Fix: preloading configuration makes signer panic at startup by @jpraynaud in #1927
- signer retrieves registrations with epoch settings route by @sfauvel in #1913
- Enhance Cardano transactions rollbacks by @jpraynaud in #1917
- Update CHANGELOG for
2437.0
distribution release by @jpraynaud in #1932 - Enhance Cardano transaction prover benchmark by @jpraynaud in #1933
- Fix: data inconsistency in Cardano transactions stores by @jpraynaud in #1936
New Contributors
- @michalrus made their first contribution in #1885
- @Mr-Leshiy made their first contribution in #1884
Full Changelog: 2430.0...2437.1
Crates Versions
Crate | Version |
---|---|
mithril-aggregator | 0.5.63 |
mithril-client | 0.8.18 |
mithril-client-cli | 0.9.12 |
mithril-client-wasm | 0.4.1 |
mithril-common | 0.4.51 |
mithril-signer | 0.2.182 |
mithril-stm | 0.3.29 |
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 <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⚠️