Mithril v2450.0

Highlights:

• 🔥 BREAKING changes in Mithril client library, CLI, and WASM:
  • Remove deprecated network field from the internal CardanoDbBeacon.
  • The Mithril certificates of type CardanoImmutableFilesFull can't be verified anymore with the previous clients.
  • Clients from distribution 2445 and earlier must be updated.
• Stable support for Cardano node 10.1.3 in the signer and the aggregator.
• Stable support for one line shell installation script of the Mithril nodes pre-built binaries.
• Bug fixes and performance improvements.

What's Changed

• Feat: custom signed entity types in backward compatibility test in CI by @jpraynaud in #2087
• Do not add unfollow files when commit with upgrade_crates_and_openapi_versions.sh by @sfauvel in #2088
• Simplify tests by @Alenar in #2090
• Refactor event message creation by @sfauvel in #2089
• Feat: add Cardano era retrieval in chain observer implementations by @dlachaume in #2094
• Docs: rotate documentation for 2445 distribution by @jpraynaud in #2079
• Docs: final CHANGELOG for '2445.0' distribution by @jpraynaud in #2096
• Docs: dev blog post for aggregator prometheus endpoint by @jpraynaud in #2095
• chore: add build target nodejs by @fabianbormann in #2082
• Prepare network removal from CardanoDbBeacon by @Alenar in #2097
• Feat: enhance certificate chain verification by @jpraynaud in #2098
• Docs: enhance runbook for aggregator metrics and signer registrations by @jpraynaud in #2099
• Feat: record informations in epoch service for status route by @dlachaume in #2100
• Docs: reorganize user manual section in docs website by @jpraynaud in #2102
• Refactor aggregator pruning with upkeep service by @sfauvel in #2103
• Refactor signer pruning with upkeep service by @sfauvel in #2108
• Feat: add genesis generate-keypair command in aggregator by @jpraynaud in #2106
• Feat: implement /status route to expose aggregator information by @dlachaume in #2107
• Remove network from CardanoDbBeacon by @Alenar in #2110
• Fix: adjust era offset in PallasChainObserver for correct display name by @dlachaume in #2112
• Add a database migration to remove network from cardano immutable files full beacons by @Alenar in #2113
• Docs: update Protocol Insights Dashboard links by @jpraynaud in #2119
• Display aggregator status information in explorer by @Alenar in #2128
• Fix for Failing STM Proptests by @curiecrypt in #2125
• fix(aggregator): properly handle 404 errors in http server by @Alenar in #2130
• Docs: dev blog post about new Protocol Insights Dashboard by @jpraynaud in #2127
• Explorer: Easier, more cohesive, aggregator controls by @Alenar in #2132
• CI: add workflow dispatcher for nightly GitHub workflows by @dlachaume in #2131
• Get rid of store adapter in signer by @sfauvel in #2126
• Docs: protocol security page on documentation website by @jpraynaud in #2133
• Feat: one line installation script for Mithril nodes by @jpraynaud in #2136
• Client wasm multiple targets by @Alenar in #2135
• Docs: dev blog post for one line installer by @jpraynaud in #2139
• Also bump versions of js packages in upgrade version script by @Alenar in #2137
• fix(ci): fix generation of swagger-ui page by @Alenar in #2141
• Feat: create new signed entity type for Incremental Cardano DB by @dlachaume in #2142
• Get rid of store adapter in aggregator by @sfauvel in #2143
• Fix Rust 1.83 clippy warnings by @Alenar in #2148
• Cardano network on aggregator status and explorer by @Alenar in #2149
• Chore: update aggregator in examples by @dlachaume in #2150
• Feat: support retries in e2e tests in CI by @jpraynaud in #2145
• Feat: implement signable builder for incremental Cardano DB by @dlachaume in #2146
• Fix: GPG verification command of released artifact by @jpraynaud in #2155
• Chore: upgrade to cardano node 10.1.3 by @jpraynaud in #2158
• Feat: add execute rights on pre-built binaries in CI by @jpraynaud in #2156
• Feat: implement artifact builder for CardanoDatabase by @dlachaume in #2159
• Docs: reorganize About Mithril section in docs website by @jpraynaud in #2160
• Chore: update dependencies for distribution 2450 by @jpraynaud in #2157
• Accelerate signer fixtures creation in tests by @sfauvel in #2161
• Chore: update dependencies for distribution 2450 by @jpraynaud in #2164
• Docs: update CHANGELOG for 2450.0 distribution release by @jpraynaud in #2163

New Contributors

• @fabianbormann made their first contribution in #2082

Full Changelog: 2445.0...2450.0

Crates Versions

Crate	Version
mithril-aggregator	0.6.0
mithril-client	0.10.4
mithril-client-cli	0.10.5
mithril-client-wasm	0.7.2
mithril-common	0.4.96
mithril-signer	0.2.221
mithril-stm	0.3.34

Networks Compatibility ⚠️

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

Distributions Compatibility ⚠️

Compatibility	mithril-signer	mithril-client
2445.0	✔️	⛔
2442.0	✔️	⛔
2437.1	✔️	⛔

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

Warning

mithril-explorer-2450.0.tar.gz checksum isn't included in the provided CHECKSUM.asc, it will be added with the next distribution.

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 ./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: 73FC 4C3D FD55 DBDC 428A D2B5 BE04 3B79 FDA4 C2EE

• 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 ⚠️