# **PIP-14: Governance Framework and DAO Council** This proposal covers a set of processes and methods as a next step forward in Panther's road towards decentralization. Furthermore, this proposal covers the introduction of the Panther Protocol DAO Council. The purpose of this proposal is to improve the DAO's Governance Framework and make it more suitable for high level, decentralized, decision making as discussed by the community on Panther's discussion forum [[1](https://forum.pantherprotocol.io/t/panther-governance-framework-proposal/234)] [[2](https://forum.pantherprotocol.io/t/pp-governance-mission-statement-mission-values-vision/254)]. Finally this proposal executes the Community Deployment Rewards as stated on [PIP-13](https://docs.pantherprotocol.io/dao/governance/proposal-13-extend-advanced-staking-and-ui-updates/compensation). ## **Summary** This proposal serves the purpose of making the Panther Protocol more decentralized. This will be achieved by: - Installing a DAO Council who will review Panther Improvement Proposals (PIPs) and decide if they will be pushed to Snapshot by verifying if the proposal draft is aligned with the mission, vision and values of the Panther DAO. The purpose of the DAO Council is to prevent requests that are out of budget, and those that do not meet the scope and roadmap of Panther as well as spam request proposals moving to Snapshot. - Turning an implicit Governance Framework into a transparent set of guidelines and rules, voted in by the Panther DAO. The identities of the DAO Council nominees are available in the proposal's description section. ## **Background** During the last few months, the Panther community has discussed the Panther Protocol Governance Framework in order to define workflows and realize a diagrammatic representation of Panther's Governance process. Because of these efforts, a set of rules and guidelines are now defined and proposed as can be seen [on the Panther Governance Framework flow diagram.](https://gateway.pinata.cloud/ipfs/QmUSRPLTf1Gm1XXX9txCAZ2ss8RzRZegsez7WbxeVyUsiu?_gl=1*1x517cz*rs_ga*NDU3MzQ1NTA5LjE2ODQ3NzM5NzI.*rs_ga_5RMPXG14TE*MTY4NDg2Nzg5Ny4yLjEuMTY4NDg2NzkwMC41Ny4wLjA.&__cf_chl_tk=ePoynwwR7HTnkS.7iT72KwRjbdlP90z2H4ktBI4YzPQ-1684868522-0-gaNycGzNEiU) ## **Description** If this proposal passes, the Panther Protocol DAO will have three council members who will be responsible for carrying out the review process within the Governance Framework for PIP submissions and labelling them based on the results of the review process as described in the DAO Governance Process. A majority vote made by the Council Members will decide if a proposal draft is being approved for voting or being rejected because it breaches the DAO Governance Rules and Values. The following DAO Governance Rules and Values are proposed: - Panther's mission is to provide privacy to an innately transparent system. Enabling confidential, trusted transactions and interoperability in Decentralized Finance (DeFi). - Panther's purpose is to build and accelerate the development of private scalable blockchain infrastructure for Web3. - Panther's vision of the world where people have access to Web3 products and services while preserving their privacy and protecting them from surveillance and maintaining composability with DeFi protocols. - Panther does not sacrifice security for innovation. - Panther stands for process and decision transparency, where every one of them is openly shared with the community. The following three community members are proposed as DAO Council members: 1. Santiago Velez: Co-Founder & Division Lead (R&D) at Block Digital Corporation, VP of R&D at Sindric Solutions, LLC Former Nuclear Engineer, VP of UWUA L590 Engineers Union and Panther Protocol user. 2. Jillian Godsil: Journalist, Broadcaster, Influencer, CEO, Writer, Former European Parliament Candidate, Law Changer, Panther Protocol user & early contributor. 3. Debra Farber: Host of The Shifting Privacy Left Podcast, CEO, Principled LLC, and Advisor to the PrivacyTech Rise, Privado, the Institute of Operational Privacy Design, and XRSI. The DAO Council will be installed for a period of 6 months, after which the community is to nominate a new list of council members. DAO Council members can be re-elected by the community. Furthermore it is proposed that the Panther DAO Council will have an operations contributor who will support the DAO Council review process and streamline the communication process between the Council and the proposal draft initiators. This proposal does not impact or change the DAO Veto Council as mentioned on the [LaunchDAO proposal](https://gateway.pinata.cloud/ipfs/QmPZ6spKQfaXdZj56zqVFMwZgHgDx2CLGcBkruN2eiYDtW). The signers of the DAO Multisig as defined on point 8 of the [launchDAO proposal](https://snapshot.org/#/launchdao.eth/proposal/0x2102148858ca04e62dddbf644d7412b114db710da97682a63a0e2d0fbd2d3bc1) remain valid and are not affected or influenced by this proposal and could be put up to vote through another, separate proposal. ## **Proposed actions** The following actions are proposed: 1. Approve the DAO Governance Process as stated in the Background section of this proposal. 2. Approve the DAO Governance Rules and Values as stated in the Description section of this proposal. 3. Approve Debra Farber, Jillian Godsil, and Santiago Velez to be the members of the Panther DAO Council in accordance with the Governance Flow Diagram as shared in the description section of this proposal. 4. Send the deployment rewards according to the points 1, 2 and 3 of the ''Community Deployment Rewards'' section of [PIP-13](https://snapshot.org/#/pantherprotocol.eth/proposal/0x0825de3b9289d3e04e8f9f3607d1145923f482104fecabc9d02634b3f7d6f521), namely: 1. The distribution of 2000 $ZKP towards the following address for deploying the updated front-end (v0.5.3) onto IPFS:0xE1B583De9cB37196031b771686734a31ec365768 2. The distribution of 6000 $ZKP to the following address who executed the blockchain transactions to deploy and configure the smart contracts on the Ethereum Mainnet and Polygon network:0xE1B583De9cB37196031b771686734a31ec365768 3. The distribution of $186.23 USD in $ZKP tokens @ ZKP=0.023 USD) as a gas fee compensation for the community member who executed point 4.2. The $ZKP/USD rate as mentioned at point 3 is updated on the day that this proposal is published on Snapshot. The Huobi [ZKP/USDT](https://www.huobi.com/en-us/exchange/zkp_usdt) pair is used to define the amount of ZKP equivalent to the gas fee compensation. The coefficient of 1.2 is used for the actual spent amount in order to compensate for possible overheads and volatility. **Participation** Please vote to accept or reject the proposed actions detailed above. Voting power is calculated by Snapshot.org taking a snapshot of the number of $ZKP tokens staked per holder [at the block within which the proposal was created.](https://docs.snapshot.org/proposals/vote) ## **Full proposal details** The full details of this proposal are visible in a more human-readable form at: https://docs.pantherprotocol.io/dao/governance/proposal-14-governance-framework-and-dao-council ## **Annex:** This proposal triggers the execution of the following blockchain transactions. These transactions are already encoded during the submission of the proposal to [Snapshot.org](https://snapshot.org/#/), and can be independently verified through the Snapshot.org web interface. The complete list of transactions can be found under the following URL: [https://docs.pantherprotocol.io/dao/governance/proposal-14-governance-framework-and-dao-council/technical-details](https://docs.pantherprotocol.io/dao/governance/proposal-14-governance-framework-and-dao-council/technical-details) ### **Batch 1 transaction 1** Mint 14100e18 $ZKP as rewards for deployment: VestingPools@eth::releaseTo(18, "0x505796f5bc290269d2522cf19135ad7aa60dfd77", "14100000000000000000000") ### **Batch 1 transaction 2** Transfer 16100e18 $ZKP to the community member who deployed and configured point 4.1 and 4.2 of the proposed actions section of this proposal: ZKPToken@eth::transfer("0xE1B583De9cB37196031b771686734a31ec365768", "16100000000000000000000") ### \*\* \*\*[ ](https://gitlab.com/pantherprotocol/deployments/-/blob/main/proposals/proposal_14/proposal_txs_data.txt)Transactions Overview: 1.1 - Mint 14100e18 $ZKPs as rewards for deployment according to PIP-13: VestingPools@eth::releaseTo(18, "0x505796f5bc290269d2522cf19135ad7aa60dfd77", "14100000000000000000000") 1.2. - Send 16100e18 $ZKPs as rewards for deployment according to PIP-13: ZKPToken@eth::transfer("0xE1B583De9cB37196031b771686734a31ec365768", "16100000000000000000000") Batch #1: ======== Tx #1.1. To: 0xb476104aa9D1f30180a01987FB09b1e96dDCF14B // VestingPools@eth Call: VestingPools@eth::releaseTo(18, "0x505796f5bc290269d2522cf19135ad7aa60dfd77", "14100000000000000000000") ABI: [{"inputs":[{"internalType":"uint256","name":"poolId","type":"uint256"},{"internalType":"address","name":"account","type":"address"},{"internalType":"uint256","name":"amount","type":"uint256"}],"name":"releaseTo","outputs":[{"internalType":"uint256","name":"released","type":"uint256"}],"stateMutability":"nonpayable","type":"function"}] params: - uint256 poolId: 18 - address account: 0x505796f5bc290269d2522cf19135ad7aa60dfd77 // DAO\_Multisig@eth, - uint256 amount: 14100000000000000000000 // 14100e18 tokens (=0x2FC5CCEDEFF8FD00000) txData: 0x2a7d7bc50000000000000000000000000000000000000000000000000000000000000012000000000000000000000000505796f5bc290269d2522cf19135ad7aa60dfd770000000000000000000000000000000000000000000002fc5ccedeff8fd00000 Tx #1.2. To: 0x909E34d3f6124C324ac83DccA84b74398a6fa173 // ZKPToken@eth Call: ZKPToken@eth::transfer("0xE1B583De9cB37196031b771686734a31ec365768", "16100000000000000000000") ABI: [{"inputs":[{"internalType":"address","name":"recipient","type":"address"},{"internalType":"uint256","name":"amount","type":"uint256"}],"name":"transfer","outputs":[{"internalType":"bool","name":"","type":"bool"}],"stateMutability":"nonpayable","type":"function"}] params: - address recipient: 0xE1B583De9cB37196031b771686734a31ec365768 - uint256 amount: 16100000000000000000000 // 16100e18 tokens (=0x368C8623A8B4D100000) txData: 0xa9059cbb000000000000000000000000e1b583de9cb37196031b771686734a31ec365768000000000000000000000000000000000000000000000368c8623a8b4d100000