CMv2 Prover Bot Funding
TL;DR
We propose to fund the operation of the CM Prover Tool during the CMv1 → CMv2 stake migration for a total of ~ 6 ETH. We expect to see about 15,000 balance-proof transactions over the migration window, and at a gas price of ~2 gwei, the total fees paid for the transactions are estimated at ~6 ETH.
A previous funding proposal for a separate instance of the same bot for CSM can be found here: CSM Prover Bot funding.
Background
The bot is the existing CSM Prover Tool, already used for CSM. It supports CMv2 via the same Verifier ABI without changes.
Its role during migration is to prove the balance deltas produced by validator consolidations described in the CMv2 migration spec, as well as to report slashings and withdrawals affecting CMv2 keys. The bot will submit a balance proof whenever a key’s unconfirmed balance delta reaches ≥ 512 ETH. Slashing and withdrawal proofs are negligible in cost at the migration scale and are covered by the same budget.
Migration scope
- ~245,000 NOR validators (32 ETH effective balance each)
- Consolidate 64:1 → 3,829 compounding validators × 2,048 ETH
- Each validator grows 32 → 2,048 ETH, covered by 4 balance proofs → 3,829 × 4 = 15,316 transactions total
4 proofs because the bot submits one whenever the unconfirmed balance delta reaches ≥ 512 ETH (its default threshold), so the 32 → 2,048 ETH growth is split into 4 increments.
Cost calculation
- Gas per
processBalanceProof: 182,939 - At a gas price of 2 gwei: the total is ~6 ETH
- Cost of a single proof: 0.000366 ETH
Funding proposal
We propose funding for the two signer addresses:
- Primary bot signer — 5.5 ETH (address:
0x4807666d701bba671032240703aaf4127ECb5c15) - Standby signer — 0.5 ETH (address:
0xC1311ceAfa96F7B2009Be23ce5e2702Abbe0D438) — used to take over processing if the primary signer gets stuck (e.g., on a transaction stalled in the mempool).