Release `2543` distribution

[jpraynaud]

Why

In order to deploy new features, improvements and bug fixes, we need to release a new distribution.

Note

The previous distribution has been created with #2625.

What

Create and release a new distribution 2543

Important

• Update constraints for mithril-common, mithril-stm (update in Cargo.toml)
• Rotate ancillary signer service account keys in release-mainnet
• Stabilize Cardano database backend next phase (https://github.com/orgs/input-output-hk/projects/26/views/14?pane=issue&itemId=118189101)
• Add AGGREGATOR_AGGREGATE_SIGNATURE_TYPE to Concatenation in GitHub environment variables (Stabilize Cardano DB v2 client CLI/library - Phase 2 #2577)
  • pre-release-preview
  • release-preprod
  • release-mainnet

Distribution +1:

Note

• Rotate ancillary signer service account keys inrelease-mainnet
• Upgrade to Cardano node 10.6.X:?
  • pre-release-preview
  • release-preprod
  • release-mainnet
• TBD

How

Phase 1: Prepare distribution

• Refresh NPM token for publication
• Run manual successful restoration of Cardano database + restart of the Cardano node:
  • Cardano DB v1
    • with ancillary
    • without ancillary
  • Cardano DB v2
    • with ancillary
    • without ancillary
• Run a backward compatibility test in the CI on the unstable distribution (with the latest built e2e test)
• Run an all green aggregator stress test in the CI
• Run an all green client multi-platform test in the CI
• Prepare a PR to upgrade repository dependencies (with runbook)
• Reset the CI caches just before merging the PR to upgrade repository dependencies
• Merge the PR to upgrade repository dependencies
• Check that all minor versions of all crates have been bumped for breaking change (if needed)
  • Bump mithril-common to 0.6
  • Bump mithril-stm to 0.5
• Check if versions of repository linked crates are correct for publication to crates.io(mithril-common, mithril-client)
• Check if Cardano minimum supported versions in networks.json must be updated following the runbook
• Create a draft PR for rotating the documentation
• Create a PR for rotating the CHANGELOG.md (set the distribution version)
• Merge the PR for rotating the CHANGELOG.md

Phase 2: Rollout pre-release distribution

• Add AGGREGATOR_AGGREGATE_SIGNATURE_TYPE to Concatenation in GitHub environment variables for pre-release-preview
• Tag and deploy a 2543.0-pre pre-release distribution on the pre-release-preview network
• Fill highlights, distributions compatibility and release notes sections in the pre-release page on GitHub
• Make sure pre-release-preview is working as expected
• Make sure Grafana dashboards are fetching data for pre-release-preview
• Make sure libraries version next have been published on npm registry
• Run an all green client multi-platform test in the CI
• Run a Cardano transaction prover benchmark:
  • Store results in the issue
  • Make sure that there is no performance drop since last release
• Announce the pre-release on discord channel
• Announce any breaking change in:
  • #cardano-scaling slack channel for pre-release
  • #mithril-lace slack channel for pre-release
  • #blockfrost-scaling slack channel for pre-release
  • #mithril-catalyst slack channel for pre-release
  • #mithril-acropolis slack channel for pre-release
  • Cardano Foundation IBC bridge team
• Wait for at least 2 signers running the new version (could be more if era change is tested) over at least 2 epochs

Phase 3: Rollout release distribution

• Tag and deploy a 2543.0 release distribution on the pre-release-preview network
• Fill highlights, distributions compatibility and release notes sections in the release page on GitHub
• Make sure pre-release-preview is working as expected
• Update networks compatibility table in release notes
• Add AGGREGATOR_AGGREGATE_SIGNATURE_TYPE to Concatenation in GitHub environment variables for release-mainnet
• Add AGGREGATOR_AGGREGATE_SIGNATURE_TYPE to Concatenation in GitHub environment variables for release-preprod
• Create a new key for the ancillary signer service account of release-mainnet
• Configure release-mainnet environment with new service account credentials
• Release the 2543.0
• Make sure release-mainnet is working as expected
• Make sure release-preprod is working as expected
• Make sure libraries have been published on crates.io
• Make sure libraries version latest have been published on npm registry
• Make sure Grafana dashboards are fetching data for release-mainnet
• Make sure Grafana dashboards are fetching data for release-preprod
• Destroy the previous key for the ancillary signer service account of release-mainnet
• Check that KMS credentials are working with the creation of the next Cardano database snapshot
• Merge the PR for rotating the documentation
• Merge a PR for rotating the CHANGELOG.md:
  • Updating the release date of the distribution
  • Updating the crate versions table
• Announce the release on discord channel (with breaking-change, upcoming features activation, ...)
• Announce any breaking/new feature change in:
  • #cardano-scaling slack channel for release
  • #mithril-lace slack channel for release
  • #blockfrost-scaling slack channel for release
  • #mithril-catalyst slack channel for release
  • #mithril-acropolis slack channel for release
  • Cardano Foundation IBC bridge team
• Update Hydra tutorial if client breaking change for database restoration
• Dev blog post:
  • Distribution 2543
  • Update the Switching to Cardano database incremental certification dev blog post

[jpraynaud]

Cardano transactions prover benchmark

Note

run on GCP with e2-highmem-2 machine with 2 vCPUs and 15GB of RAM
not during Cardano database snapshotting

• Benchmark results:

total_requests	concurrency	transactions/request	requests/s
500	50	1	76.03
500	50	10	54.50
500	50	20	40.82
500	50	30	33.53
500	50	40	25.74
500	50	50	26.43

vs previous results

total_requests	concurrency	transactions/request	requests/s
500	50	1	73.09
500	50	10	48.18
500	50	20	41.54
500	50	30	36.94
500	50	40	29.50
500	50	50	23.04

• Command run:

# Aggregator endpoint
export AGGREGATOR_ENDPOINT=https://aggregator.pre-release-preview.api.mithril.network/aggregator

# Transactions file to prove
export TRANSACTIONS_FILE=transactions-preview.txt

# Transactions proved per request range definition
export TRANSACTIONS_PER_REQUEST_MIN=0
export TRANSACTIONS_PER_REQUEST_MAX=50
export TRANSACTIONS_PER_REQUEST_STEP=10

# Apache benchmark total request sent per benchmark
export AB_TOTAL_REQUESTS=500

# Apache benchmark concurrency level range definition
export AB_CONCURRENCY_MIN=50
export AB_CONCURRENCY_MAX=50
export AB_CONCURRENCY_STEP=50

# Run the benchmark:
./benchmark-aggregator-prover.sh

• Command result:

MITHRIL AGGREGATOR PROVER ROUTE BENCHMARK

>> Aggregator endpoint: https://aggregator.pre-release-preview.api.mithril.network/aggregator
>> Aggregator route: /proof/cardano-transaction
>> Transactions file: transactions-preview.txt
>> Transactions available: [100]
>> Transactions per request range: [0 10 20 30 40 50]
>> AB concurrency range: [50]
>> AB total requests per run: [500]
>> AB total runs: 6
>> Output file: benchmark.csv

>> [#1/6] Running stress test with 500 requests with 1 transactions per request and 50 concurrency
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests
>>>> Success (73.09 requests/s)

>> [#2/6] Running stress test with 500 requests with 10 transactions per request and 50 concurrency
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests
>>>> Success (48.18 requests/s)

>> [#3/6] Running stress test with 500 requests with 20 transactions per request and 50 concurrency
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests
>>>> Success (41.54 requests/s)

>> [#4/6] Running stress test with 500 requests with 30 transactions per request and 50 concurrency
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests
>>>> Success (36.94 requests/s)

>> [#5/6] Running stress test with 500 requests with 40 transactions per request and 50 concurrency
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests
>>>> Success (29.50 requests/s)

>> [#6/6] Running stress test with 500 requests with 50 transactions per request and 50 concurrency
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests
>>>> Success (23.04 requests/s)

>> Benchmark completed:

total_requests,concurrency,transactions/request,requests/s
500,50,1,73.09
500,50,10,48.18
500,50,20,41.54
500,50,30,36.94
500,50,40,29.50
500,50,50,23.04