The proposal on the previous page is based on the intention that a follow-on DAO proposal should be made very soon after this proposal is approved and executed, most likely within a matter of days, to finalize the implementation of this Polygon package.
The purpose of this follow-on proposal will be to extend DAO governance and staking (including rewards) to Polygon, so that the utility of $ZKP on Polygon is much the same as it currently is on Ethereum mainnet:
Holders of $ZKP on Polygon will be able to stake on Polygon as part of the existing “traditional” staking program.
Holders of $ZKP who have staked on Polygon will have the ability to participate in Panther Governance proposals, with the same voting powers as those who have staked on the Ethereum mainnet.
Add configuration to the existing Ethereum mainnet staking contracts to allow an alternative option of staking without rewards. This will allow the Panther Foundation to stake without taking rewards from the existing “traditional” staking program.
This document proposes the initial steps of extending the Panther Protocol, DAO, and ecosystem to the Polygon PoS network:
Launch a ZKP token contract at 0x9A06Db14D639796B25A6ceC6A1bf614fd98815EC
on the Polygon PoS mainnet, to operate in parallel alongside the existing ZKP token contract at 0x909e34d3f6124c324ac83dcca84b74398a6fa173
on the Ethereum mainnet.
Request the Polygon team to set up a mapping between these two contracts, so that anyone will be able to use the existing Polygon PoS bridge to move tokens between the two networks in either direction, subject to execution of item 4 below.
Approve the Panther DAO multisig contract (Gnosis Safe) at 0x208Fb9169BBec5915722e0AfF8B0eeEdaBf8a6f0
on the Polygon PoS mainnet, configured in a manner which effectively extends the DAO’s control from the Ethereum mainnet to Polygon (see below for technical details).
Execute a transaction on the Ethereum mainnet via Reality.eth. It will use the Polygon Arbitrary Message Bridge to send a transaction from the Ethereum Mainnet to Polygon PoS to transfer control of the minter role within the new Polygon ZKP token contract to the Polygon bridge.
This proposal was accepted with 99.92% of the vote on March 4th, 2022.
The Panther Foundation will compensate for the cost of "gas" on the Ethereum network to any person who executes the transaction which fulfills this proposal, by sending 500 $ZKP tokens to the Ethereum address the transaction was sent from.
To clarify, this only applies to the Reality.eth transactions directly associated with this DAO proposal, which are listed at the corresponding page on snapshot.org. It does not promise any compensation for normal staking / unstaking transactions, or other interactions with the smart contracts.
The new DAO multisig Gnosis Safe contract on Polygon PoS will have the following properties:
It will be configured with an implementation of the Zodiac Reality Module, enhanced for compatibility with Polygon. This will allow it to receive and execute transactions which come from DAO proposals executed on the Ethereum mainnet and are passed over the Polygon AMB (Arbitrary Message Bridge).
It will be configured with the same DAO multisig signers as the existing DAO multisig on the Ethereum mainnet.
In order for "Zodiac Reality Module" (further referred to as the "Module") to execute a transaction, any corresponding proposal must have passed, as reported by Reality.eth.
The Reality.eth question should conform to this template (the required template ID is defined by the installed Module):
"title": "Did the Snapshot proposal with the id %s in the PantherProtocol.eth space pass the execution of the array of Module transactions that have the hash 0x%s and does it meet the requirements of the document referenced in the daorequirements record at PantherProtocol.eth? The hash is the keccak of the concatenation of the individual EIP-712 hashes of the Module transactions. If this question was asked before the corresponding Snapshot proposal was resolved, it should ALWAYS be resolved to INVALID!",
"category": "DAO proposal"
Reality.eth should resolve the question to “yes” only for proposals that:
had a minimum quorum of 4% of the $ZKP token total supply, returned by the $ZKP smart contract deployed on Ethereum network at the address stated by the zkpaddress
record at PantherProtocol.eth (https://app.ens.domains/name/pantherprotocol.eth/details), having cast votes to approve execution of the transactions;
had a voting period of at least 3 days;
had no significant service outages or availability issues that could have reasonably restricted $ZKP token holders from casting their votes in the proposal;
have a minimum bond on the Reality question of at least 0.5ETH;
the module transaction hash in the Reality.eth question is the keccak hash of the concatenation of the individual EIP-712 hashes of the module transactions defined in the Snapshot proposal;
the plain description of the transactions, and their intended result, in the proposal is complete and accurate;
do not occur during, in, or as a result of any unauthorized or malicious changes to the PantherProtocol.eth Snapshot space;
were not filtered from the default view in the PantherProtocol.eth Snapshot space during the voting period.
Reality.eth should resolve the question to “invalid” if:
the Reality.eth question meets the above requirements but was created prior to the end of the proposal vote period and/or the Snapshot block for the vote (i.e. the final results of the vote are not yet known).
In all other cases, the Reality.eth question should be resolved to “no”.