Skip to content

Releases: input-output-hk/mithril

Mithril v2437.0-pre

12 Sep 08:22
@github-actions github-actions
2437.0-pre
a248dd9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Mithril v2437.0-pre Pre-release
Pre-release

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 with client.
  • 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 skips RollForward 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 for mithril-client crate by @Mr-Leshiy in #1884
  • Chore: post Chang hard fork cleanup by @jpraynaud in #1912
  • Refactor: seamless unstable to stable 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

New Contributors

Full Changelog: 2430.0...2437.0-pre

Crates Versions

Crate Version
mithril-aggregator 0.5.62
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.181
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 <[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 ⚠️

Contributors

Alenar, sfauvel, and 5 other contributors
Assets 13
Loading

Mithril v2430.0

30 Jul 08:07
@github-actions github-actions
2430.0
52a7beb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Mithril v2430.0

Highlights:

  • Support for Cardano node 9.1.0.
  • Support for Cardano transactions certification in release-preprod and pre-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 Cardano 9.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 in Certificate & 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 on find_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 ⚠️

Contributors

Alenar, sfauvel, and 2 other contributors
Assets 13
Loading

Mithril v2430.0-pre

26 Jul 09:53
@github-actions github-actions
2430.0-pre
52a7beb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Mithril v2430.0-pre Pre-release
Pre-release

Highlights:

  • Support for Cardano node 9.1.0.
  • Support for Cardano transactions certification in release-preprod and pre-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 Cardano 9.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 in Certificate & 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 on find_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-pre

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

Contributors

Alenar, sfauvel, and 2 other contributors
Assets 13
Loading

Mithril v2428.0

15 Jul 09:46
@github-actions github-actions
2428.0
6756b0f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Mithril v2428.0

Highlights

  • Support for Cardano node 9.0.0.
  • Database cleanup and optimization once per epoch.
  • Bug fixes and performance improvements.

What's Changed

  • Remove manual workflow step for old snapshot commands availability by @dlachaume in #1734
  • Fix: make prover not certify transactions stored but not certified yet by @jpraynaud in #1721
  • Add Makefiles to facilitate the update of www and www-test dependencies by @dlachaume in #1735
  • Add tooling to verify example conformity in openapi.yaml by @sfauvel in #1728
  • Refactor timepoint retrieval & conversion to signed entities by @Alenar in #1736
  • feat(tls): Allow the underlying TLS implementation to be selected by feature flags. by @stevenj in #1738
  • Update CHANGELOG with 2423.0 distribution release by @jpraynaud in #1733
  • docs: add missing pre-requisites for building crates by @jpraynaud in #1740
  • Remove bottleneck in proof generation of Merkle map by @jpraynaud in #1739
  • Sqlite auto rollback by @Alenar in #1742
  • Rotate documentation for 2423 distribution by @jpraynaud in #1732
  • Update CHANGELOG with 2423.0 distribution release by @jpraynaud in #1745
  • Dev blog post for removed snapshot command in client CLI by @jpraynaud in #1746
  • Implement pooled resource item reset when given back by @jpraynaud in #1744
  • Handle rollbacks when reading blocks from the chain by @Alenar in #1748
  • fix: clippy warnings with Rust 1.79.0 by @jpraynaud in #1749
  • Signed entity lock mechanism by @Alenar in #1758
  • Use macOS-arm64 runner in CI by @dlachaume in #1752
  • Fix macOS-arm64 architecture value from lowercase to uppercase in CI by @dlachaume in #1759
  • Upgrade doc dependencies by @dlachaume in #1764
  • Warmup/Preload cardano transactions & block range roots by @Alenar in #1763
  • Upgrade mithril-explorer, www and www-test dependencies by @dlachaume in #1765
  • Upgrade project dependencies by @dlachaume in #1768
  • Add Mithril Threat Model page on website by @jpraynaud in #1726
  • Import transactions in sequence on signer by @Alenar in #1769
  • Implement database connection pooling for Cardano transaction store by @jpraynaud in #1761
  • Only save rust cache on main branch by @Alenar in #1770
  • Add missing pre-requisites to build WASM client by @dlachaume in #1772
  • Ensure validation of transaction hashes to provide to the prover by @dlachaume in #1774
  • Vacuum sqlite database at startup & after transactions preload by @Alenar in #1771
  • Add MSYS2 building instructions by @jasagredo in #1773
  • Use a macro to limit error in default configuration by @sfauvel in #1778
  • Fix #1762: CardanoTransactionSnapshot block number is not certified by @Alenar in #1779
  • Fix: avoid iterator copy in BlockRangeRootRetriever by @jpraynaud in #1780
  • Import Cardano transactions with Pallas chain reader by @jpraynaud in #1747
  • Fix aggregator Cardano transaction prover benchmark tool by @jpraynaud in #1790
  • Conditional embedding cardano cli in docker image by @sfauvel in #1789
  • Fix sanchonet blocks parsing by @jpraynaud in #1794
  • Upkeep service for aggregator & signer by @Alenar in #1791
  • Support Cardano node 8.12.2 by @jpraynaud in #1788
  • Fix: aggregator and signer blocked during Cardano transactions import by @jpraynaud in #1798
  • Fix: Support Cardano 8.12 by @jpraynaud in #1799
  • Bugfix: Can't generate proof for transactions on the last signed block number by @Alenar in #1795
  • Preload Cardano transactions based on Aggregator's Signing Capability by @dlachaume in #1796
  • Fix explorer crash when proving transaction & enhance mithril-client error by @Alenar in #1800
  • Standardize code formatting in repository by @dlachaume in #1783
  • Fix: avoid pool acquire timeout during Cardano transaction prover cache computation by @jpraynaud in #1801
  • UpkeepService tests flakiness by @Alenar in #1802
  • Refactor: Cardano node configuration in infra by @jpraynaud in #1806
  • Support Cardano node 9.0.0 by @jpraynaud in #1809
  • Remove call to chain observer on pending certificate route by @sfauvel in #1808
  • Update CHANGELOG with 2428 distribution release by @jpraynaud in #1812
  • Upgrade dependencies by @jpraynaud in #1811

New Contributors

Full Changelog: 2423.0...2428.0

Crates Versions

Crate Version
mithril-aggregator 0.5.40
mithril-client 0.8.7
mithril-client-cli 0.9.6
mithril-client-wasm 0.3.7
mithril-common 0.4.29
mithril-signer 0.2.161
mithril-stm 0.3.24

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, co...
Read more

Contributors

stevenj, Alenar, and 4 other contributors
Assets 13
Loading

Mithril v2428.0-pre

11 Jul 08:14
@github-actions github-actions
2428.0-pre
6756b0f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Mithril v2428.0-pre Pre-release
Pre-release

Highlights

  • Support for Cardano node 9.0.0.
  • Database cleanup and optimization once per epoch.
  • Bug fixes and performance improvements.

What's Changed

  • Remove manual workflow step for old snapshot commands availability by @dlachaume in #1734
  • Fix: make prover not certify transactions stored but not certified yet by @jpraynaud in #1721
  • Add Makefiles to facilitate the update of www and www-test dependencies by @dlachaume in #1735
  • Add tooling to verify example conformity in openapi.yaml by @sfauvel in #1728
  • Refactor timepoint retrieval & conversion to signed entities by @Alenar in #1736
  • feat(tls): Allow the underlying TLS implementation to be selected by feature flags. by @stevenj in #1738
  • Update CHANGELOG with 2423.0 distribution release by @jpraynaud in #1733
  • docs: add missing pre-requisites for building crates by @jpraynaud in #1740
  • Remove bottleneck in proof generation of Merkle map by @jpraynaud in #1739
  • Sqlite auto rollback by @Alenar in #1742
  • Rotate documentation for 2423 distribution by @jpraynaud in #1732
  • Update CHANGELOG with 2423.0 distribution release by @jpraynaud in #1745
  • Dev blog post for removed snapshot command in client CLI by @jpraynaud in #1746
  • Implement pooled resource item reset when given back by @jpraynaud in #1744
  • Handle rollbacks when reading blocks from the chain by @Alenar in #1748
  • fix: clippy warnings with Rust 1.79.0 by @jpraynaud in #1749
  • Signed entity lock mechanism by @Alenar in #1758
  • Use macOS-arm64 runner in CI by @dlachaume in #1752
  • Fix macOS-arm64 architecture value from lowercase to uppercase in CI by @dlachaume in #1759
  • Upgrade doc dependencies by @dlachaume in #1764
  • Warmup/Preload cardano transactions & block range roots by @Alenar in #1763
  • Upgrade mithril-explorer, www and www-test dependencies by @dlachaume in #1765
  • Upgrade project dependencies by @dlachaume in #1768
  • Add Mithril Threat Model page on website by @jpraynaud in #1726
  • Import transactions in sequence on signer by @Alenar in #1769
  • Implement database connection pooling for Cardano transaction store by @jpraynaud in #1761
  • Only save rust cache on main branch by @Alenar in #1770
  • Add missing pre-requisites to build WASM client by @dlachaume in #1772
  • Ensure validation of transaction hashes to provide to the prover by @dlachaume in #1774
  • Vacuum sqlite database at startup & after transactions preload by @Alenar in #1771
  • Add MSYS2 building instructions by @jasagredo in #1773
  • Use a macro to limit error in default configuration by @sfauvel in #1778
  • Fix #1762: CardanoTransactionSnapshot block number is not certified by @Alenar in #1779
  • Fix: avoid iterator copy in BlockRangeRootRetriever by @jpraynaud in #1780
  • Import Cardano transactions with Pallas chain reader by @jpraynaud in #1747
  • Fix aggregator Cardano transaction prover benchmark tool by @jpraynaud in #1790
  • Conditional embedding cardano cli in docker image by @sfauvel in #1789
  • Fix sanchonet blocks parsing by @jpraynaud in #1794
  • Upkeep service for aggregator & signer by @Alenar in #1791
  • Support Cardano node 8.12.2 by @jpraynaud in #1788
  • Fix: aggregator and signer blocked during Cardano transactions import by @jpraynaud in #1798
  • Fix: Support Cardano 8.12 by @jpraynaud in #1799
  • Bugfix: Can't generate proof for transactions on the last signed block number by @Alenar in #1795
  • Preload Cardano transactions based on Aggregator's Signing Capability by @dlachaume in #1796
  • Fix explorer crash when proving transaction & enhance mithril-client error by @Alenar in #1800
  • Standardize code formatting in repository by @dlachaume in #1783
  • Fix: avoid pool acquire timeout during Cardano transaction prover cache computation by @jpraynaud in #1801
  • UpkeepService tests flakiness by @Alenar in #1802
  • Refactor: Cardano node configuration in infra by @jpraynaud in #1806
  • Support Cardano node 9.0.0 by @jpraynaud in #1809
  • Remove call to chain observer on pending certificate route by @sfauvel in #1808
  • Update CHANGELOG with 2428 distribution release by @jpraynaud in #1812
  • Upgrade dependencies by @jpraynaud in #1811

New Contributors

Full Changelog: 2423.0...2428.0-pre

Crates Versions

Crate Version
mithril-aggregator 0.5.40
mithril-client 0.8.7
mithril-client-cli 0.9.6
mithril-client-wasm 0.3.7
mithril-common 0.4.29
mithril-signer 0.2.161
mithril-stm 0.3.24

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 ✔️...
Read more

Contributors

stevenj, Alenar, and 4 other contributors
Assets 13
Loading

Mithril v2423.0

12 Jun 07:56
@github-actions github-actions
2423.0
665621d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Mithril v2423.0

Highlights:

  • 🔥 BREAKING changes in Mithril client CLI:
    • The deprecated snapshot command has been removed.
    • It has been superseded by the cardano-db command.
  • Bug fixes and optimizations.

What's Changed

Full Changelog: 2418.1...2423.0

Crates Versions

Crate Version
mithril-aggregator 0.5.16
mithril-client 0.8.3
mithril-client-cli 0.9.2
mithril-client-wasm 0.3.3
mithril-common 0.4.13
mithril-signer 0.2.141
mithril-stm 0.3.22

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

Contributors

Alenar, sfauvel, and 4 other contributors
Assets 12
Loading

Mithril v2423.0-pre

06 Jun 08:36
@github-actions github-actions
2423.0-pre
665621d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Mithril v2423.0-pre Pre-release
Pre-release

Highlights:

  • 🔥 BREAKING changes in Mithril client CLI:
    • The deprecated snapshot command has been removed.
    • It has been superseded by the cardano-db command.
  • Bug fixes and optimizations.

What's Changed

Full Changelog: 2418.1...2423.0-pre

Crates Versions

Crate Version
mithril-aggregator 0.5.16
mithril-client 0.8.3
mithril-client-cli 0.9.2
mithril-client-wasm 0.3.3
mithril-common 0.4.13
mithril-signer 0.2.141
mithril-stm 0.3.22

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

Contributors

Alenar, sfauvel, and 4 other contributors
Assets 12
Loading

Mithril v2418.1

13 May 09:20
@github-actions github-actions
2418.1
512fe8d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Mithril v2418.1

Highlights:

  • ⚠️ BREAKING changes in Mithril client / Mithril client CLI:
    • Certificate chain structure has been modified to remove coupling with immutable file number.
    • Client must be updated to verify certificate chain.
  • Switched memory allocator to jemallocator on signer and aggregator to avoid memory fragmentation.
  • Always enabled BLST portable feature for runtime check of intel ADX instruction set.

What's Changed

Full Changelog: 2412.0...2418.1

Crates Versions

Crate Version
mithril-aggregator 0.5.0
mithril-client 0.8.0
mithril-client-cli 0.8.0
mithril-client-wasm 0.3.0
mithril-common 0.4.0
mithril-signer 0.2.130
mithril-stm 0.3.19

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

Contributors

Alenar, sfauvel, and 2 other contributors
Assets 12
Loading

Mithril v2418.1-pre

30 Apr 08:16
@github-actions github-actions
2418.1-pre
512fe8d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Mithril v2418.1-pre Pre-release
Pre-release

Highlights:

  • ⚠️ BREAKING changes in Mithril client / Mithril client CLI:
    • Certificate chain structure has been modified to remove coupling with immutable file number.
    • Client must be updated to verify certificate chain.
  • Switched memory allocator to jemallocator on signer and aggregator to avoid memory fragmentation.
  • Always enabled BLST portable feature for runtime check of intel ADX instruction set.

What's Changed

Full Changelog: 2412.0...2418.1-pre

Crates Versions

Crate Version
mithril-aggregator 0.5.0
mithril-client 0.8.0
mithril-client-cli 0.8.0
mithril-client-wasm 0.3.0
mithril-common 0.4.0
mithril-signer 0.2.130
mithril-stm 0.3.19

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

Contributors

Alenar, sfauvel, and 2 other contributors
Assets 12
Loading

Mithril v2418.0-pre

29 Apr 13:09
@github-actions github-actions
2418.0-pre
dd881df
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Mithril v2418.0-pre Pre-release
Pre-release

Highlights:

  • ⚠️ BREAKING changes in Mithril client / Mithril client CLI:
    • Certificate chain structure has been modified to remove coupling with immutable file number.
    • Client must be updated to verify certificate chain.
  • Switched memory allocator to jemallocator on signer and aggregator to avoid memory fragmentation.
  • Always enabled BLST portable feature for runtime check of intel ADX instruction set.

What's Changed

Full Changelog: 2412.0...2418.0-pre

Crates Versions

Crate Version
mithril-aggregator 0.4.66
mithril-client 0.7.4
mithril-client-cli 0.7.12
mithril-client-wasm 0.2.6
mithril-common 0.3.36
mithril-signer 0.2.130
mithril-stm 0.3.19

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

Contributors

Alenar, sfauvel, and 2 other contributors
Assets 12
Loading