feat(zk_toolbox): Deploy ConsensusRegistry (BFT-504)

[aakoshh]

What ❔

Adds a zk_inception chain deploy-consensus-registry command.

TODO:

• Change contracts submodule back to main once feat: Deploy ConsensusRegistry through L1 to L2 transaction (BFT-504) era-contracts#735 is merged

Contract Owner

The agreement was that on testnet the ConsensusRegistry contract should be owned by the governor account, which is 0xD64e136566a9E04eb05B30184fF577F52682D182, while on mainnet it should be owned by the developer multisig account.

The owner is set in DeployL2ContractsInput::consensus_registry_owner which has access to contract and wallet configuration and these are written to a config file just before deployment.

I added an optional developer_multisig wallet to WalletConfig, so the address can be added at the same place as the governor address is; if developer_multisig is missing then governor is used. I suppose it could be made part of the ContractsConfig instead, but since this is a wallet with funds that developers can access, I thought it wouldn't be out of place in wallets.yaml even if one doesn't have any of the corresponding private keys. Let me know if I should be using something else.

Testing

Since the zk_toolbox is replacing the zk commands, and zk init doesn't deploy the consensus registry, we have to use the following commands to see that the contract is built, deployed and its address is written to the config file:

./bin/zkt
zk_inception ecosystem create
zk_inception containers
zk_inception ecosystem init --dev

After this we can check if we see the address in the generated config file:

❯ cat ./chains/era/configs/contracts.yaml | yq .l2.consensus_registry
0x72ada8c211f45e768c9a7781793da84daf1d0d1b

Finally clean up:

zk_supervisor clean all

Why ❔

So that we can deploy the L2 consensus registry contract using the zk_toolbox.

Checklist

• PR title corresponds to the body of PR (we generate changelog entries from PRs).
• Tests for the changes have been added / updated.
• Documentation comments have been added / updated.
• Code has been formatted via zk fmt and zk lint.