[BIP-341] Set Escrow Re-mapper Manager for Tetu

Governance
1

PR with Payloads

Motivation:
To enable Tetu to have Cross chain boost

Specification:

  1. The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will initiate a transaction to interact with the Authorizer 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6 calling grantRole with the following arguments:

role: 0x6bb341db03eede206e544c654a59ef89eea83bc65fada2cfeeaf18c5c0f76ac0 which corresponds to the role for calling setNetworkRemappingManager on the VotingEscrowRemapper, verifiable here.

account: 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f

which corresponds to the DAO Multisig. This allows the multisig to call the above function.

  1. The DAO multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with VotingEscrowRemapper at 0x83E443EF4f9963C77bd860f94500075556668cb8 (verifiable here 1) calling setNetworkRemappingManager with the values

localUser: 0x9cC56Fa7734DA21aC88F6a816aF10C5b898596Ce (Tetu veBAL Locker)
delegate: eth:0x4bE13bf2B983C31414b358C634bbb61230c332A7 (Tetu mainnet multisig)

  1. The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will finally initiate a transaction to interact with the Authorizer 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6 calling revokeRole after successfully granting the votingEscrow remapper roles to the Tetu veBAL locker and Tetu mainnet multisig.

This grants the ability to call setNetworkRemapping to the Tetu Multisig, allowing Tetu to set their own L2 boost addresses.

2 Likes
2

I added a revokeRole argument to the specifications as we don’t want to permanetly grant this role to the multi-sig for security reasons.

3

https://snapshot.org/#/balancer.eth/proposal/0xca340ee235248add30302eab3b017894a772eb7e89b6fe1032521c9bc6775ef1