JBP-371 - Migrate Multisig JBX -> v3

Author: filipv
Date: 2023-04-15

Thesis

Migrate all of the JuiceboxDAO multisig's v1 JBX to v3 JBX.

Why

To consolidate the DAO's JBX for simpler operations.

Specification

1. Call v1 OperatorStore.setOperator(...) with an _operator of JBV3Token, a _domain of 1, and a _permissionIndexes of [12] (Transfer).
2. Call v2 JBOperatorStore.setOperator with an operator of JBV3Token, a domain of 1, and a permissionIndexes of 12 (Transfer).
3. Call Tickets.approve(...) on v1 JBX with a spender of JBV3Token and the maximum amount (the maximum UINT256, 2**256 - 1).
4. Call JBV3Token.migrate().

Rationale

1. Allows the JBV3Token contract to migrate the DAO's v1 JBX.
2. Allows the JBV3Token contract to migrate the DAO's v2 JBX.
3. Allows the JBV3Token contract to migrate the DAO's v1 Tickets ERC-20 JBX.
4. Migrates the tokens approved in steps 1-3.

Risks

Although the v3 migration contracts were tested and audited, there are always risks of bugs and vulnerabilities when interacting with smart contracts.

Timeline

To be executed within 90 days of this proposal's Snapshot ratification.

---

Discussion Thread | IPFS