As you might know by now, we are on our way to Panther Protocol’s mainnet release. After years of developing and testing the protocol, it is now time for the DAO to prepare for its launch. Panther Protocol has been decentralized from its inception. Through a decentralized TGE called the launchDAO and the decentralized deployment and configuration of Panther Protocol’s Advanced Staking protocol, the Panther community has demonstrated its ability to manage the Panther DAO for multiple years. And now, as an ecosystem, we must ensure that the DAO can continue to do this for years to come.
Over the last year, we at Panther Protocol primarily focused on the testnet and the limited mainnet beta launch, which resulted in the last Panther Improvement Proposal (PIP-20) being voted in approximately one and a half years ago. Therefore, it makes sense to check if the current Snapshot admins (multisig) and authors are still active members of the DAO and community. And if not, a refresh makes sense to ensure that the DAO is in good shape and fully operational before Panther’s mainnet launch - and the Panther Protocol Foundation is here to help!
We would like to bring up the following action items:
Ensuring that all signers of the multisig are active and willing to do their part
Reassess the Snapshot authors to determine if a refresh is necessary. One and a half years is a long time in crypto, and the active Panther Protocol community has likely undergone significant changes.
Raw markdown of IPFS files for the PIPs. For each published Panther DAO Improvement Proposal, there’s a raw markdown file required. We have set up a tutorial on how to create one here. Don’t worry, it’s easier than you think!
The consideration of a DAO advisory panel consisting of community members, privacy advocates, and industry spokespersons. We have experimented with an advisory panel before, and we would like your opinion on the concept of having a few contributors with specific experience and expertise helping the Panther community with proposals. Of course, the advisory panel holds no real power and is merely here to assist the Panther DAO (and, in turn, $ZKP holders) with the proposals themselves and assess their impact before the proposal drafts are put up for a vote.
Ensuring that the voting quorum is still effective after this long cooldown period of one and a half years of no DAO activity. Given that the last PIP was voted in a while ago, the voting activity expressed in $ZKP may be lower than before, which means that it could potentially be harder to reach the quorum. A discussion about this would make sense - we would love to hear your thoughts!
Also, please let us know if we missed any action items. We aim to announce the testnet airdrop and provide more information, as well as a recap of the limited mainnet beta rewards distribution. Once these two have been completed and the Panther Protocol DAO is in good shape, the Panther ecosystem should be ready for its long-awaited mainnet launch. Onwards!
Re point 2, if would propose that we ask our Telegram community members if they are interested in becoming Snapshot authors to ensure that the influence of the active community members increase. This would also be great for the sustainability of the DAO.
Out of my head, these 3 authors (out of 5) are no longer active community members:
Mibrody (Discord: MIBrody#2617), well-known Community member. Address: 0x9E2A8e8Be6a0049D14C10be4a1854a06A72e25d0
Marcus, (Discord: marcusrc#0226), well-known Community member. Address: 0xdfc8cE21F67FBC4115DAddCdC740948BD8fAe317
Markus, (Discord: Markus_KK#6674 ), well-known Community member. Address: 0xF68813feF24Ae1CE7000f0f1771Cd3042d5702be
Of course, please correct me if I am wrong
So we could use 3 new community members there. There should be an incentive for them to help the protocol succeed. I think that Marrco, Elysium, MM, Hakan, or Malcolm for example would be great candidates.
I would propose that we wrap up the above in a formal Panther Improvement Proposal (PIP) somewhere next week, given that we have 3 awesome candidates as new authors.
Great - we still have to discuss the voting QUORUM requirement any suggestions there? I see there is over 26 million ZKP in HTX, in excess of 10 million in MEXC and a serious amount of the tokens are stuck in the advanced staking protocol.
I think that this is a good idea, given that reaching the voting quorum was an (unnecessary) pain point in the past. Due to the one and a half years of testing the protocol, and therefore a lack of supply distribution (due to no live mainnet), I think that it would make sense to lower the voting quorum from 4% of the total circulating $ZKP supply to 2% of the total circulating $ZKP supply. This way, a minimum amount of $ZKP is still required for voting in a new PIP, but it’s well within reach.
PIP-21: Revising Snapshot Authors and Adjusting Voting Quorum
Background
This proposal aims to prepare the DAO for Panther Protocol’s mainnet launch by revising some of its Snapshot authors and adjusting the voting quorum from 4% of the total circulating supply to 2%.
Description
Updating the Snapshot authors ensures that the number of active Panther Protocol community members who can publish Panther Improvement Proposals (PIPs) is maintained by replacing inactive community members. Adjusting the voting quorum from 4% of the total circulating supply to 2% would mean that roughly 7.521.798,56 $ZKP (7.5 million) needs to be put up for a vote on a Panther Improvement Proposal (PIP) rather than approximately 15 million $ZKP that is required currently.
If this proposal passes, the Panther Protocol Space will have 3 new whitelisted Authors.
Section #1: Remove the following Snapshot Authors
This proposal involves removing the right to introduce Panther Improvement Proposals (PIPs) in Panther’s Snapshot.org space from the following Snapshot Authors:
Mibrody (Discord: MIBrody#2617), well-known Community member. Address: 0x9E2A8e8Be6a0049D14C10be4a1854a06A72e25d0
Marcus, (Discord: marcusrc#0226), well-known Community member. Address: 0xdfc8cE21F67FBC4115DAddCdC740948BD8fAe317
Markus, (Discord: Markus_KK#6674 ), well-known Community member. Address: 0xF68813feF24Ae1CE7000f0f1771Cd3042d5702be
Section #2: Introduce new Snapshot Authors
Markhobbit (Discord: @markhobbit360), well-known Community member. Address:
0xC745dD3E29ec5d28634AF588D5dd50a2c3Efb6A4
Gulum_ZKP (Discord: X), well-known Community member. Address:
0x86CEf673a8eF51DCF92E1a699128Fb12f6C0C0D8
Scott_W (Discord: S.W), well-known Community member. Address: TBC
Section #3: Send the deployment rewards related to PIP-20, namely:
The distribution of 5200 $ZKP towards the following address for deploying the updated front-end (v0.5.6) onto 0xE1B583De9cB37196031b771686734a31ec365768
The distribution of 5200 $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
The distribution of $132 USD in $ZKP tokens - which is $ZKP 14667 at the rate $ZKP=0.009 USD - as a gas fee compensation for the community member who executed point 3 of the Proposed Actions section, PIP-20: :0xE1B583De9cB37196031b771686734a31ec365768
Summary
This will update the current Snapshot authors to:
Victor, (Discord: Black322#9757), Discord community admin. Address: 0xDC885850D72c3269aa2d2bCB32C70E2080b3ACF1
Toxic Entity, (Discord: toxicehc#5599), well-known Community member. Address: 0xE1B583De9cB37196031b771686734a31ec365768
Markhobbit (Discord: @markhobbit360), well-known Community member. Address:
0xC745dD3E29ec5d28634AF588D5dd50a2c3Efb6A4
Gulum_ZKP (Discord: @.reaper), well-known Community member. Address:
0x86CEf673a8eF51DCF92E1a699128Fb12f6C0C0D8
Scott_W (Discord: S.W), well-known Community member. Address: TBC
Proposed Actions
The following actions are proposed:
Update the list of Snapshot Authors as described in the Sections #1 and #2.
Adjust the voting quorum from 4% of the total circulating supply to 2%.
