| Title | Deactivate Capped Minters for TPP1 Ignite |
|---|---|
| Proposal Type | TPP |
| One Sentence Summary | This proposal removes the minter role from Ignite Program capped minters. |
| Proposal Author | Baptiste (Merkl) |
| Proposal Sponsor | Baki |
| Submitted onchain | TBC |
| Version | v1 |
| Summary of Action | Revoke Minter Role from all Ignite Program capped minters to prevent further minting. |
| Link to forum post | n/a |
| Link to contracts | n/a |
Simple Summary
This proposal removes the minter role from Ignite Program capped minters.
Abstract
Now that the Ignite Program has concluded, the Token Assembly will ensure that no remaining unminted supply in the affiliated program or admin capped minters can be minted. This proposal includes the call data required to revoke the minter role from all capped minters linked to the Ignite Program.
Motivation
Cancellation of Token Programs using the ZkCappedMinterV1 can be done in one of two ways:
- Sending the admin multisig control to a burn address; or
- Revoking the Minter Role via a Token Assembly proposal.
The DSC multisig is required to remain active to complete unclaimed token reallocations. As such, a Token Assembly-approved proposal is necessary to revoke the Minter Role from Ignite capped minters.
Please note that the limitations considered here are specific to the Ignite Program deployed with ZkCappedMinterV1 contracts.
For future token programs, the ZkCappedMinterV2 contracts allow the deactivation of a ZkCappedMinterV2 through the admin controlled cancel() function. Please refer to the following documentation for more information.
Impact
This proposal ensures the safety and security of the remaining unminted supply in each capped minter. Neither the DeFi Steering Committee multisig or any other actor who would be able to gain access the multisig would be able to mint any further tokens from the Ignite Program Capped Minters.
Mechanic
This proposal would include the revokeRole() call on each of the following Ignite Program capped minters.
| Capped Minter | Address | Total Cap (ZK) | Remaining Cap (ZK) |
|---|---|---|---|
| IP-ZK-Distro-Minter-1 | 0xe546AEaaC57584da7554e7F88154DeDAD30A82b0 | 50,000,000 | ~11,492,378 |
| IP-ZK-Distro-Minter-2 | 0x11791c6249631555cEb75CB39128789E3954c2EC | 50,000,000 | ~37,582,899 |
| IP-ZK-Distro-Minter-3 | 0x3BC3f64d084bE6d3336f10340DC8424290FFc4ab | 50,000,000 | 50,000,000 |
| IP-ZK-Distro-Minter-4 | 0xDa2fBE31Fd47Af741bdB3dBC4eb662dA0107D33a | 50,000,000 | 50,000,000 |
| IP-ZK-Distro-Minter-5 | 0x6b689B93B368c7C25E6e5ecaeAb23C11F8C2c392 | 50,000,000 | 50,000,000 |
| IP-ZK-Distro-Minter-6 | 0x2CC6c7b1a59A23fB3faCAFe4A3791C5c8A58Cbcc | 50,000,000 | 50,000,000 |
| IP-ZK-Admin-Minter-OBL | 0xD375A20d93C2F7C6a83B19C5ae153cF2C6e09ba9 | 4,995,500 | 2,811,028 |
| IP-ZK-Admin-Minter-Merkl | 0x2ADa5C15BC4FEE97EC2463ce4F8E4557174B8Dcf | 4,634,500 | 3,707,600 |
| IP-ZK-Admin-Minter-DSC | 0x4E86e74237Eb1f9432810eB5ab5861368d2f5964 | 3,250,000 | 2,890,000 |
| IP-ZK-Admin-Minter-Supporting-Services | 0x178bFf5A197FB4499526D04Db602C45cEDCA40a9 | 12,120,000 | 18,230,349 |
| Total Amount of ZK in Capped Minters | 325,000,000 | ~276,714,254 |
Plan & Accountability
If the proposal is passed, there will be no further action or oversight required to prevent further minting from the Ignite Program capped minters.
Other Information
Original Proposal: [TPP-001] ZKsync Ignite Program: Creating a Liquidity Hub for ZKsync
Program Cancellation: ZKsync Ignite Cancellation