Release 2450 distribution

[jpraynaud]

Why

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

What

Create and release a new distribution 2450

Important

• 🔥 Announce breaking change in clients
• 🔥 recompute certificate chain
  • in pre-release-preview
  • in release-preprod
  • in release-mainnet
• Upgrade to Cardano node 10.1.3
  • in pre-release-preview
  • in release-preprod
  • in release-mainnet
• Pre-built binaries have execution rights
• New NodeJS npm package
• Activate Cardano stake distribution certification:
  • in release-mainnet

Distribution +1:

Note

• TBD

How

Phase 1: Prepare distribution

• Run a backward compatibility test in the CI
• Upgrade repository dependencies (with runbook)
• Check that all minor versions of all crates have been bumped for breaking change (if needed)
• 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
• Merge a PR for rotating the CHANGELOG.md (set the distribution version)
• Create a draft PR for rotating the documentation

Phase 2: Rollout pre-release distribution

• Update the configuration of pre-release-preview:
  • Upgrade the Cardano node version to 10.1.3 in pre-release-preview
• Tag and deploy a 2450.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
• Recompute the certificate chain of pre-release-preview
• Make sure pre-release-preview is working as expected
• Make sure libraries version next have been published on npm registry
• Run an all green client multi-platform test in the CI
• Run an all green aggregator stress 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
  • #minotaur-mithril slack channel for pre-release
  • Cardano Foundation IBC bridge team
• Wait for at least 3 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 2450.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
• Update the configuration of release-preprod:
  • Upgrade the Cardano node version to 10.1.3 in release-preprod
• Update the configuration of release-mainnet:
  • Upgrade the Cardano node version to 10.1.3 in release-mainnet
• Release the 2450.0 distribution
• Recompute the certificate chain of release-mainnet
• Make sure release-mainnet is working as expected
• Recompute the certificate chain of release-preprod
• 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
• Merge the PR for rotating the documentation
• Merge a PR for rotating the CHANGELOG.md (updating the release date of the distribution)
• 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
  • #minotaur-mithril slack channel for pre-release
  • Cardano Foundation IBC bridge team
• Dev blog post:
  • Enhanced explorer status?
  • TBD

Phase 4: Activate features

• Cardano stake distribution:
  • When signer release >= 0.2.182 (2437.1) is run by > 95% of the stake (within 2 weeks, or abort),
  • Activate the certification of Cardano stake distribution in release-mainnet
  • Restart the release-mainnet deployment in the CI
  • Make sure release-mainnet is working as expected
  • Announce the release on discord channel
  • Dev blog post: Activation of Cardano stake distribution in release-mainnet

[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	52.48
500	50	10	39.06
500	50	20	32.82
500	50	30	29.57
500	50	40	25.39
500	50	50	23.15

vs previous results

total_requests	concurrency	transactions/request	requests/s
500	50	1	53.93
500	50	10	39.81
500	50	20	25.17
500	50	30	29.80
500	50	40	23.59
500	50	50	21.11

• 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 (52.48 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 (39.06 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 (32.82 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 (29.57 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 (25.39 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.15 requests/s)

>> Benchmark completed:

total_requests,concurrency,transactions/request,requests/s
500,50,1,52.48
500,50,10,39.06
500,50,20,32.82
500,50,30,29.57
500,50,40,25.39
500,50,50,23.15