Author

desnake

Summary

This proposal aims to aks DAO’s approval of transactions executed as a [GIP-235] implementation, which included deployment of system contracts, whitelisting auditors and activating first 6 instances.

In addition it asks DAO approval to activate World Chain instance.

Specification

GIP-235 execution report

Due to a small flaw in deployment of the system contracts connected to Cross Chain Multisig and Instance Manager at the addresses outlined in GIP-235 developers had to redeploy those contracts which resulted in its new addresses:

• Cross Chain Multisig address: 0xcCCCCcCc42B7DA9fdEc1761698Fb55fdD41CDF55
• Instance Manager address: 0x77777777144339Bdc3aCceE992D8d4D31734CB2e

3 batches were signed by Technical Multisig members in Cross Chain multisig (0xcCCCCcCc42B7DA9fdEc1761698Fb55fdD41CDF55).

Parsed batches in readable form can be found in Permissionless interface -> Cross Chain Multisig -> History (https://permissionless.gearbox.foundation/crosschain). The aforementioned frontend is maintained by Gearbox Contributors and is designed serve as a unified interface for managing the whole Permissionless system.

This GIP passing will mean DAO’s approval of the executed transactions and the resulting state of corresponding smart contracts.

World Chain instance activation

It’s proposed to activate World Chain Instance with the following parameters: Chain ID: 480 Treasury: 0xef78F5FfD8c6c5aa45bCAb7f4BA638B0A4fbc7A1 IO: 0x1E9ec044853611F4bCD4BBcFE7657508BD1c53D3 WETH: 0x4200000000000000000000000000000000000006 GEAR: 0x0000000000000000000000000000000000000000

Execution

It’s proposed to sign the txn listed above by the Technical Multisig optimistically as soon as it’s possible. Instance activation doesn’t create risks to any funds. This structure is proposed to be able to execute the activation earlier, as it must be timed with Gearbox’s and World Chain’s bd & marketing efforts.