Below the draft for PIP-29:
Proposal Overview
Rewards Minting & Vesting Implementation - PIP-29
This proposal invites the Panther DAO community to discuss and determine the amount of ZKP to be minted for the V1 privacy rewards pool, and the associated vesting schedule. The funds will support protocol incentives and PRP redemption, with a compliance-driven structure. The mint will also include the previously approved 1,000,000 $ZKP for the Subsidy Pool and 100,000 $ZKP for initial Rewards pool AMM liquidity. Additionally, this proposal appoints Anish as a member of the Emergency Stop Committee, as established in PIP-25.
Motivation
-
With the upcoming V1 DAO zone launch, it is necessary to fund the rewards pool so that users who contribute assets to Panther’s privacy set can earn PRP and redeem PRP for ZKP. These rewards are designed for active protocol participation and are directly tied to privacy set growth.
-
It is suggested to use a minting and vesting framework similar to the previous Canary network launch; for example, 8 million $ZKP distributed over 4 months, with a community review after 3 months to assess ongoing rewards, mint amounts, and vesting parameters.
-
In accordance with the vote on PIP-26, the proposal incorporates 1,000,000 $ZKP for the Subsidy Pool and 100,000 $ZKP for AMM liquidity, alongside whatever further amount and vesting schedule the DAO community determines.
-
The proposal also adds Anish Mohammed to the Emergency Stop Committee, completing the addition begun after the previous vote in PIP-25.
ETH: 0x1F8988053F13c92d248F6eCba59A1C85dcFE4ceF
Proposed Changes
1. Privacy Rewards Pool Minting
-
The DAO will discuss and establish the total ZKP to be minted and the vesting schedule for the V1 rewards pool.
-
PRP can be redeemed for ZKP, awarded for verifiable contributions to the Panther privacy set, per PIP-26 parameters.
-
The inclusion of 1M $ZKP for Subsidy Pool And 100,000 $ZKP for the Initial rewards pool AMM,
As defined in PIP-26 parameters. -
Minting and vesting parameters are open for community discussion—with initial guidance to follow approaches used in the Canary network.
2. Emergency Stop Committee Membership
- Anish Mohammed to be added to the Emergency Stop Committee (as defined in PIP-25).
3. Code Executions For PIP-25:
Emergency Stop Multisig introduction:
A new Emergency Stop Multisig will be introduced. This multisig will have the authority to trigger a single transaction—the “emergency stop”—but it won’t have the ability to perform any other actions, except to enable the “reality.eth” module - all via the DAO multisig’s “guard” module.
Admin Multisig will enable/disable reality.eth plugin:
An existing Admin Multisig will be allowed to enable or disable the “reality.eth” module on the DAO Multisig. However, the Admin Multisig will not have any other powers with the DAO Multisig. Again, the “guard” module will be used on the DAO multisig to control this.
Removal of Old Veto Council:
The members of the old Veto Council will be removed as signers from the DAO multisig. After this change, the DAO multisig will be fully controlled by plugins (e.g., “reality.eth” and guards), and no human signers will be involved in its operation.
—
Funding
- Rewards will be sourced from the 450M $ZKP protocol rewards allocation.
Next Steps
-
Community members are encouraged to discuss appropriate ZKP minting amount and vesting schedule.
-
Voting: PIP-29 will be published on Snapshot for a 3-day vote. Voting eligibility per PIP-7.