Mithril v2335.0-pre

What's Changed

• TW review of references.md by @olgahryniuk in #1134
• ECS-3077 Apply style guide, tighten some sentences. by @NeilBurgess42 in #1130
• ECS-3078 review certificates.md, the description of the certificate c… by @NeilBurgess42 in #1135
• ECS-3079 Review simulation document, apply style guide, some suggesti… by @NeilBurgess42 in #1136
• ECS-3111 Apply style guide, minor changes. by @NeilBurgess42 in #1143
• TW review of: aggregator.md & signer.md by @olgahryniuk in #1145
• ECS-3112 Review architecture.md, apply style guide. by @NeilBurgess42 in #1144
• ECS-3115 Review client.md, apply IOG style guide. by @NeilBurgess42 in #1146
• Better unpack error in client by @jpraynaud in #1148
• Reorganize docs folder by @jpraynaud in #1150
• Implement prometheus monitor for end to end tests by @jpraynaud in #1139
• Upgrade explorer to next 13 by @Alenar in #1149
• Add network production runbooks for Aggregator by @jpraynaud in #1086
• Registered signers page to explorer by @Alenar in #1157
• Download latest snapshot & stake distribution if latest is mentioned in Mithril Client commands by @dlachaumepalo in #1110
• fnv/core verifier by @curiecrypt in #939
• ECS-3156 Review glossary. Adjust capitalization and bolding. by @NeilBurgess42 in #1158
• StdResult and StdError as anyhow alias by @Alenar in #1162
• Protocol key for Operational Certificate by @dlachaumepalo in #1161
• Upgrade dependencies by @Alenar in #1163
• Protocol key for verification key signature by @dlachaumepalo in #1164
• Regression on signer registration by @Alenar in #1166
• Simplify logs by @Alenar in #1165
• Protocol key for genesis keys by @dlachaumepalo in #1167
• Fix broken .#hydraJobs.x86_64-linux.mithril-end-to-end by @yvan-sraka in #1168
• Call Aggregator API to verify Signer registration by @dlachaumepalo in #1169
• Protocol key for AVK by @Alenar in #1170
• Protocol key for era keys by @Alenar in #1171
• Client snapshot download progress with json output by @Alenar in #1172
• Fix run-signer-node doc by @dlachaumepalo in #1175
• Rust version 1.72.0 : fix cargo clippy warning & update dependencies by @dlachaumepalo in #1176
• Add network compatiblity table to autogenerated releases by @Alenar in #1177
• Fix network compatibility table generation by @Alenar in #1180
• Replace git switch with git checkout in docs by @dlachaumepalo in #1178
• Fix verify archive in aggregator Snapshotter by @jpraynaud in #1179
• Fix latest digest usage in documentation by @jpraynaud in #1182
• Fix flaky end to end test by @jpraynaud in #1181
• Download unpack snapshots simultaneously by @Alenar in #1183
• Aggregator stress test refactoring by @jpraynaud in #1186
• Fix disk space warning not displayed in client by @jpraynaud in #1192
• Add common error: CodecError by @dlachaumepalo in #1193
• Upgrade ed25519-dalek to v2 by @Alenar in #1189

New Contributors

• @NeilBurgess42 made their first contribution in #1130
• @yvan-sraka made their first contribution in #1168

Full Changelog: 2331.1...2335.0-pre

Crates Versions

Crate	Version
mithril-aggregator	0.3.76
mithril-client	0.3.38
mithril-common	0.2.100
mithril-signer	0.2.72
mithril-stm	0.3.1

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