Jean-Philippe Raynaud

I completely agree with keeping `mithril-core` agnostic and handle the certification of the `Mithril Verification Keys` and `PoolId` in `mithril-common` instead :+1: We will use the code you created in...

> There is a `CardanoNetwork` enum in mithril-common used in `BeaconProvider` & `CliObserver`. IMHO the enum variant `CardanoNetwork::TestNet` should be changed to `Preview` as well. Actually, the parameters used with...

The `Mithril Aggregator` hosted on GCP now runs on the `preview` network and has produced its first snapshot :+1: To make a `Mithril Signer` work on this network, here is...

Many thanks @Alenar for your large contribution to this PR and for all the help and support you provided :1st_place_medal:

Hi @pgwadapool, thanks for your feedback :slightly_smiling_face: Could send us the following information so that we can identify the issue? * Steps to reproduce * System info * Full logs...

It looks like there are some permissions issues with your remote docker setup. Unfortunately, we have not been able to reproduce the problem on our end. Can you provide us...

Hi @pgwadapool thanks for your feedback, I close the issue :+1:

Same bug noticed on the Hydra CI: https://github.com/input-output-hk/mithril/pull/1472/checks?check_run_id=21007590367 ``` failures: ---- utils::progress_reporter::tests::check_seconds_elapsed_in_json_report_with_more_than_100_milliseconds stdout ---- thread 'utils::progress_reporter::tests::check_seconds_elapsed_in_json_report_with_more_than_100_milliseconds' panicked at mithril-client-cli/src/utils/progress_reporter.rs:160:9: Not expected value in json output: {"timestamp": "2024-01-26T11:20:10.550875+00:00", "bytes_downloaded": 0, "bytes_total":...

Same bug noticed on the GitHub Actions CI: https://github.com/input-output-hk/mithril/actions/runs/7757675676/job/21157694463#step:5:851 ``` Summary [ 167.911s] 811 tests run: 810 passed (2 slow), 1 failed, 0 skipped FAIL [ 0.010s] mithril-client-cli utils::progress_reporter::tests::check_seconds_elapsed_in_json_report_with_more_than_100_milliseconds ---...

Since we have implemented the era mechanism, the behavior of the aggregator node at startup has changed and partially mitigated this issue: the era reader reads an Utxo on the...