Mithril v2430.0
Highlights:
- Support for Cardano node
9.1.0
. - Support for Cardano transactions certification in
release-preprod
andpre-release-preview
. - Bug fixes and performance improvements.
What's Changed
- Configure Cardano transaction signing parameters with CI/CD by @jpraynaud in #1815
- Fix Signer
make test
command errors by @dlachaume in #1817 - Fix: Explorer keep previous error until refresh in cardano transaction certification modal by @Alenar in #1824
- Fix: missing configuration in terraform deployment action in CI/CD by @jpraynaud in #1821
- Rotate documentation for
2428
distribution by @jpraynaud in #1823 - Update CHANGELOG for
2428.0
distribution release by @jpraynaud in #1827 - Respin
testing-sanchonet
with Cardano9.0.0
by @jpraynaud in #1829 - Bugfix: Block range computation ignored last block range & last block range if it finished with empty blocks by @Alenar in #1820
- Fix formatting error in Mithril Signer node documentation by @dlachaume in #1831
- Remove
task::block_in_place
in transaction importer by @Alenar in #1805 - Ensemble/1792/non blocking artifact production in aggregator by @sfauvel in #1828
- Add metrics table in the "Activate Prometheus endpoint" section by @dlachaume in #1833
- Make upper bound of
ChainReaderBlockStreamer
inclusive by @Alenar in #1835 - Ensemble/1825/cleanup immutable file in cardano transation by @sfauvel in #1838
- Make deprecated
beacon
field optional inCertificate
&CertificateList
messages by @Alenar in #1839 - fix: Resource not Reset when given back to Pool by @jpraynaud in #1848
- Replace
BlockNumber
alias with dedicated structure by @Alenar in #1846 - fix:
ChainReader
fails onfind_intersect_point
without agency by @jpraynaud in #1852 - fix: clippy warnings with Rust
1.80.0
by @jpraynaud in #1857 - Support Cardano node
9.1.0
by @jpraynaud in #1856 - Replace
SlotNumber
alias with dedicated structure by @sfauvel in #1854 - Upgrade infrastructure deployment with disk configurations by @jpraynaud in #1850
- Upgrade
release-mainnet
aggregator VM data disk by @jpraynaud in #1859 - Upgrade Rust dependencies by @jpraynaud in #1858
- Update CHANGELOG for
2430
distribution release by @jpraynaud in #1860
Full Changelog: 2428.0...2430.0
Crates Versions
Crate | Version |
---|---|
mithril-aggregator | 0.5.50 |
mithril-client | 0.8.10 |
mithril-client-cli | 0.9.9 |
mithril-client-wasm | 0.3.8 |
mithril-common | 0.4.38 |
mithril-signer | 0.2.170 |
mithril-stm | 0.3.26 |
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⚠️