Panther Protocol: proposal for the launch of $ZKP and other smart contracts

Voting ended about 4 years agoSucceeded

Panther is an interoperable privacy solution focused on the needs of DeFi users of all kinds and sizes.

Panther Protocol aims to be a truly decentralized protocol, governed from the start by its users and community via a decentralized launch. This proposal serves to bootstrap the launch of the Panther token and the activation of its vesting contract, minting, and initial distribution of $ZKP on Ethereum as per the details provided below.
As a member of the valued Panther community who has successfully completed KYC, you are being invited to participate in the exclusive Panther LaunchDAO. Voting in this very first proposal will also earn you rewards in the form of $ZKP, minted if the vote results in the launch of the protocol.

The Panther team and Foundation will not be participating in the vote and have no control over its outcome.

In alignment with our core mission, the voting process will use zero-knowledge proofs to ensure the privacy of all launch participants. Users who register will receive a new, non-transferable “$PreZKP” token on Polygon.$PreZKP allows users to participate in the Voting process.

The main points of this Proposal include:

To start the minting and vesting of the ZKP token to the following 13 pools with the mentioned parameters:

(Pools: Protocol Rewards, Foundation General, Foundation - Reserves, Foundation Bug Bounties, Foundation Education & Awareness, Pre-Seed Backers, Seed Backers, Priv Sale 1, Priv Sale 2, Priv Sale 3, Pub Sale Opt 1, Pub Sale Op 2, Early Team + Advisors; Params: start date, duration, number of tokens, initially unlocked)

To distribute tokens from the vesting pools classified as “Foundation General”, “Foundation - Reserves”, “Foundation Bug Bounties”, “Foundation Education & Awareness”, according to the vesting schedule with the parameters stated below, to a multi-signature wallet for the Foundation created for this purpose.
To distribute tokens from the Private Sale rounds pools, according to the vesting schedule with the parameters stated below.
To distribute tokens from the Public Sale rounds pools, according to the vesting schedule in the Public Sale option that includes vesting.
To set privileged roles with smart contracts (which allow for updates to existing smart contract configuration and additions of new smart contracts to the protocol) to holders of ZKP tokens collectively, via the mechanism of off-chain voting on protocol governance proposals via Snapshot.org
To set up a voting system in such a way that to vote on a governance proposal a holder of ZKP tokens must stake the token to a special governance staking contract with a minimum staking period of 7 days. These special staking contracts will also generate Staking Rewards to Stakers. As of now, the number of $ZKP to be allocated per 3 months period for Staking Rewards is capped at 5M $ZKP originating from the “Protocol Rewards” allocation. The reason for this number is because the total Protocol Reward also includes rewards for Privacy Staking and transacting within Shielded Pools - which is a part of the main protocol that is not released yet.
To protect, take corrective actions and minimize the risks caused by smart contract bugs, etc. This proposal will allow a set of signers of the DAO multisig to have an overrule power.

Below are the details of the Contract and token distribution:

Mint and vest $ZKP tokens on the Ethereum Mainnet as follows. 1.1. Token symbol and standard Token standard: ERC20. Token symbol: $ZKP. Maximum supply: 1,000,000,000 tokens. Token contract address: see below. Minting and vesting schedule: as defined below. 1.2. Minting and vesting parameters Initiate the following distribution of $ZKP tokens, by executing Ethereum transactions, which calls addVestingPools method on the VestingPools smart contract instance. Interpretation of parameters

Note: There are around 50 Private Sale investors who are undergoing a compliance check and therefore not in the below list. The total sum of tokens for these addresses will be minted and stored in a multisig wallet <0x15eE5348793618F5Fb9D859F24275afe07Dd5054> owned by Panther Ventures Limited and upon compliance approval, they will be released or sent. Interpretation of parameters

Use the following smart contracts. The following smart contracts on the Ethereum mainnet to be used as the core of the Panther Protocol. 2.1. Addresses of smart contracts: at 0x909E34d3f6124C324ac83DccA84b74398a6fa173 - referred to as the ZKPToken at 0xb476104aa9D1f30180a01987FB09b1e96dDCF14B - VestingPools at 0x4A4FC40d2475f493EcA3Ec436b924237AA1b0a76 - PoolStakes implementation at 0xF62837d4EbF3D0309E32bAF55919d4371900e6B5 - Pre-Seed Bakers pool wallet at 0xBc9Dff00b1950dAc0185B5e986748637EaBd9BC5 - Seed Bakers pool wallet at 0x40E92E8c3D2a5BAcdED54af444CAF820a9F480B0 - Private Sale 1 pool wallet at 0xD90354a7437D36550cb21e17a9A3feeFB0c92b87 - Private Sale 2 pool wallet at 0x5CDabc5a62F7F6387488E7195686059509739aAF - Private Sale 3 pool wallet At 0xcF463713521Af5cE31AD18F6914f3706493F10e5 - RewardPool contract at 0x505796f5bc290269d2522cf19135ad7aa60dfd77 - DAO Multisig at 0xa3c955d317E2E13B490f71c20AD248f91F5d5511 - DAO Multisig Extension at 0xEb5B192CDCDa4Ba0500D426A0f330d958A733280 - Foundation Multisig at 0x7bd49ed57289e2aae3cedD18339204131fad98bB - Public Sales Multisig at 0xFe1c87f24A091bB729033c3522C039566477Eb1c - Company Multisig 2.2. "Roles" (hierarchy) of smart contracts: DAO Multisig has the role of the owner with the VestingPools DAO Multisig has the role of the owner (and/or defaultOwner) with the PoolStakes VestingPools has the role of the minter with the ZKPToken
Transfer control over smart contracts to $ZKP tokens holders. Transfer control over smart contracts to holders of $ZKP as follows. Configure the DAO Multisig to have privilege roles with other smart contracts, so that transactions sent from the former may configure parameters of the latest ones; Enable DAO Multisig Extension to execute transactions from the DAO multisiq on the Ethereum network; Configure DAO Multisig Extension to execute only those transactions which passed voting under proposals in the PantherProtocol.eth space on the Snapshot.org service in accordance to the "Panther Protocol: Proposal Acceptance Criteria" document, published on the IPFS network with the cid defined by the daorequirements record at PantherProtocol.eth; Configure the PantherProtocol.eth space on the Snapshot.org service so that it computes voting power of $ZKP tokens holders calculated as "one token - one vote".
Compensate execution of the proposal. Compensate costs of "gas" on Ethereum network to any person who executes transactions under the present proposal, with 500 $ZKP tokens payable to the Ethereum address the transactions have been sent from.

Off-Chain Vote

For

2.56K 98.6%

Against

23 0.9%

Abstain

13 0.5%

Download mobile app to vote

Timeline

Dec 31, 2021Proposal created

Dec 31, 2021Proposal vote started

Jan 02, 2022Proposal vote ended

Oct 26, 2023Proposal updated

Panther is an interoperable privacy solution focused on the needs of DeFi users of all kinds and sizes.

The Panther team and Foundation will not be participating in the vote and have no control over its outcome.

The main points of this Proposal include:

To start the minting and vesting of the ZKP token to the following 13 pools with the mentioned parameters:

To distribute tokens from the vesting pools classified as “Foundation General”, “Foundation - Reserves”, “Foundation Bug Bounties”, “Foundation Education & Awareness”, according to the vesting schedule with the parameters stated below, to a multi-signature wallet for the Foundation created for this purpose.
To distribute tokens from the Private Sale rounds pools, according to the vesting schedule with the parameters stated below.
To distribute tokens from the Public Sale rounds pools, according to the vesting schedule in the Public Sale option that includes vesting.
To set privileged roles with smart contracts (which allow for updates to existing smart contract configuration and additions of new smart contracts to the protocol) to holders of ZKP tokens collectively, via the mechanism of off-chain voting on protocol governance proposals via Snapshot.org
To set up a voting system in such a way that to vote on a governance proposal a holder of ZKP tokens must stake the token to a special governance staking contract with a minimum staking period of 7 days. These special staking contracts will also generate Staking Rewards to Stakers. As of now, the number of $ZKP to be allocated per 3 months period for Staking Rewards is capped at 5M $ZKP originating from the “Protocol Rewards” allocation. The reason for this number is because the total Protocol Reward also includes rewards for Privacy Staking and transacting within Shielded Pools - which is a part of the main protocol that is not released yet.
To protect, take corrective actions and minimize the risks caused by smart contract bugs, etc. This proposal will allow a set of signers of the DAO multisig to have an overrule power.

Below are the details of the Contract and token distribution:

Mint and vest $ZKP tokens on the Ethereum Mainnet as follows. 1.1. Token symbol and standard Token standard: ERC20. Token symbol: $ZKP. Maximum supply: 1,000,000,000 tokens. Token contract address: see below. Minting and vesting schedule: as defined below. 1.2. Minting and vesting parameters Initiate the following distribution of $ZKP tokens, by executing Ethereum transactions, which calls addVestingPools method on the VestingPools smart contract instance. Interpretation of parameters

Use the following smart contracts. The following smart contracts on the Ethereum mainnet to be used as the core of the Panther Protocol. 2.1. Addresses of smart contracts: at 0x909E34d3f6124C324ac83DccA84b74398a6fa173 - referred to as the ZKPToken at 0xb476104aa9D1f30180a01987FB09b1e96dDCF14B - VestingPools at 0x4A4FC40d2475f493EcA3Ec436b924237AA1b0a76 - PoolStakes implementation at 0xF62837d4EbF3D0309E32bAF55919d4371900e6B5 - Pre-Seed Bakers pool wallet at 0xBc9Dff00b1950dAc0185B5e986748637EaBd9BC5 - Seed Bakers pool wallet at 0x40E92E8c3D2a5BAcdED54af444CAF820a9F480B0 - Private Sale 1 pool wallet at 0xD90354a7437D36550cb21e17a9A3feeFB0c92b87 - Private Sale 2 pool wallet at 0x5CDabc5a62F7F6387488E7195686059509739aAF - Private Sale 3 pool wallet At 0xcF463713521Af5cE31AD18F6914f3706493F10e5 - RewardPool contract at 0x505796f5bc290269d2522cf19135ad7aa60dfd77 - DAO Multisig at 0xa3c955d317E2E13B490f71c20AD248f91F5d5511 - DAO Multisig Extension at 0xEb5B192CDCDa4Ba0500D426A0f330d958A733280 - Foundation Multisig at 0x7bd49ed57289e2aae3cedD18339204131fad98bB - Public Sales Multisig at 0xFe1c87f24A091bB729033c3522C039566477Eb1c - Company Multisig 2.2. "Roles" (hierarchy) of smart contracts: DAO Multisig has the role of the owner with the VestingPools DAO Multisig has the role of the owner (and/or defaultOwner) with the PoolStakes VestingPools has the role of the minter with the ZKPToken
Transfer control over smart contracts to $ZKP tokens holders. Transfer control over smart contracts to holders of $ZKP as follows. Configure the DAO Multisig to have privilege roles with other smart contracts, so that transactions sent from the former may configure parameters of the latest ones; Enable DAO Multisig Extension to execute transactions from the DAO multisiq on the Ethereum network; Configure DAO Multisig Extension to execute only those transactions which passed voting under proposals in the PantherProtocol.eth space on the Snapshot.org service in accordance to the "Panther Protocol: Proposal Acceptance Criteria" document, published on the IPFS network with the cid defined by the daorequirements record at PantherProtocol.eth; Configure the PantherProtocol.eth space on the Snapshot.org service so that it computes voting power of $ZKP tokens holders calculated as "one token - one vote".
Compensate execution of the proposal. Compensate costs of "gas" on Ethereum network to any person who executes transactions under the present proposal, with 500 $ZKP tokens payable to the Ethereum address the transactions have been sent from.