Mithril v2331.1-pre
Pre-release
Pre-release
github-actions
released this
08 Aug 10:04
·
4496 commits
to main
since this release
What's Changed since 2331.0-pre
- Speedup node bootstrap after client download by @Alenar in #1132
- Add snapshot archive verification by @jpraynaud in #1138
- Clean ssh keys of infrastructure by @jpraynaud in #1142
Full Changelog: 2331.0-pre...2331.1-pre
What's Changed since 2329.0
- Fix crates versions not shown in release notes by @jpraynaud in #1070
- Minor editing tweaks to 'Welcome' by @olgahryniuk in #1068
- nix: improve caching strategy to share deps among artifacts. by @jbgi in #1069
- Tech writing review by @olgahryniuk in #1067
- Add
release-mainnet
configuration in documentation and explorer by @jpraynaud in #1065 - Update current documentation by @jpraynaud in #1072
- Add dev blog post for
mainnet
Beta launch by @jpraynaud in #1074 - nix: fix build of common/stm, improve caching by @jbgi in #1077
- Ensemble/668/refacto crypto entities by @ghubertpalo in #1075
- Bundle openssl with released binaries by @Alenar in #1079
- fix verification key (de)serialization by @ghubertpalo in #1088
- TW review by @olgahryniuk in #1087
- Update Mainnet Beta Launch dev blog post by @jpraynaud in #1084
- Enhance Mithril relay configuration by @jpraynaud in #1089
- Remove legacy store adapters & fix prune of stake pool & epoch settings by @Alenar in #1076
- Add
sign
sub-command in aggregatorgenesis
command by @jpraynaud in #1082 - Update dependencies by @jpraynaud in #1093
- Enhance Run a Mithril Signer as an SPO guide by @dlachaumepalo in #1071
- Greg/668/single signature by @ghubertpalo in #1107
- Upgrade Cardano node to
8.1.2
by @jpraynaud in #1092 - Common protocol key type for serialization of Stm types by @Alenar in #1108
- Factorize hardcoded keys by @Alenar in #1109
- Update Mainnet Beta Launch dev blog post by @jpraynaud in #1113
- Getting started: capitalization edits by @olgahryniuk in #1119
- TW review of mithril-aggregator.md by @olgahryniuk in #1117
- Curiecrypt/resolve flaky test by @curiecrypt in #1105
- TW review of mithril-signer.md by @olgahryniuk in #1120
- TW review of mithril-client.md by @olgahryniuk in #1121
- Update
README
by @jpraynaud in #1118 - Update current documentation by @jpraynaud in #1123
- Protocol key for Multi and Genesis signature by @Alenar in #1124
- Simplify epoch type by implementing Deref & TryInto by @Alenar in #1126
- Aggregator Stress Test - Phase 1 by @jpraynaud in #1062
- Ingest metrics/logs in Grafana by @jpraynaud in #1128
- Add signers registered route to aggregator by @Alenar in #1129
- Speedup node bootstrap after client download by @Alenar in #1132
- Add snapshot archive verification by @jpraynaud in #1138
- Clean ssh keys of infrastructure by @jpraynaud in #1142
Full Changelog: 2329.0...2331.1-pre
Networks Compatibility ⚠️
Network | Compatible |
---|---|
release-mainnet |
⛔ |
release-preprod |
⛔ |
pre-release-preview |
✔️ |
testing-preview |
✔️ |
Crates Versions
Crate | Version |
---|---|
mithril-aggregator | 0.3.67 |
mithril-client | 0.3.27 |
mithril-common | 0.2.89 |
mithril-signer | 0.2.65 |
mithril-stm | 0.2.20 |
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 gpg-public.key and save it in the same folder as the asset
- Step 6: Then import the GPG public key:
gpg --import ./gpg-public.key
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 ./gpg-public.key ./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⚠️