Proposal #13: Extend Advanced Staking and UI Updates

Summary:

This proposal introduces two key initiatives:

1. Extending the "Advanced Staking" program till August 22, 2023. The parameters of the program can be found in the "Terms for smart contracts" section.
2. Activating updates to the front-end (UI) of Panther Protocol (version 0.5.1). A list of updates can be found in the v0.5.3 release description.

Background:

1. The initial "Advanced Staking" program was launched via PIP-9 and PIP-10 and successfully reached its end on 07 April, 2023. There are remaining $ZKP tokens originally allocated as staking rewards that the community proposes to use to reward stakers in the extended program.
2. As discussed on Panther's Discourse forum, the community recommends running a new cycle of the "Advanced Staking" program (AS2), with parameters stated below in the "Terms for smart contracts" section.

This proposal authorizes and triggers the execution (via Panther's space on Snapshot.org and the Reality.eth oracle) of the attached blockchain transactions listed below under Annex, deploying and configuring Panther's smart contracts to launch AS2.

Through PIP-11 Panther's front-end v0.5.1 was deployed and activated. After the launch, users witnessed minor front-end (UI) related issues. Contributors to the protocol prepared, tested, and released the new front-end version - v0.5.3.

The community recommends using the v0.5.3 front-end instead of v0.5.1 (the previous one).

In order to have a user-friendly URL pointing to v0.5.3's front-end, and to safeguard access to the correct link/app, the community makes a recommendation to configure the pantherprotocol.eth ENS domain namespace in such a way that the user-friendly link https://ipfs.io/ipns/pantherprotocol.eth will point to the v0.5.3 front-end.

Terms for smart contracts:

It is proposed to follow the below parameters for extending the "Advanced Staking" program:

Parameter	Description
Last day stakes are accepted	August 22, 2023 12:00:00 PM UTC. This can be earlier should "Amount of $ZKP allocated for rewards to all stakers" (see PIP-9) get depleted or Panther's v1 be launched beforehand.
Time for a staker to withdraw rewards from the MASP (but forfeiting the right to accumulate PRPs)	Immediately after the stake is created.

Other parameters remain the same as defined by PIP-9.

Community Deployment Rewards:

Users who (1) deploy the v0.5.3 front-end to IPFS and (2) execute blockchain transactions listed in the Annex shall be rewarded as follows:

1. 2,000 $ZKP shall be rewarded to each of the first 2 deployers of the updated front-end (v0.5.3) to IPFS.
2. 6,000 $ZKP shall be rewarded to the user(s) who execute the blockchain transactions to deploy and configure smart contracts on the Ethereum Mainnet and Polygon network. There are 6 transactions to execute, each one will award a user 1,000 $ZKP reward.
3. Users who execute the mentioned above blockchain transactions shall be given extra rewards as compensation for the gas costs incurred by these users on the Ethereum Mainnet.

To clarify, this only applies to the Reality.eth transactions directly associated with this DAO proposal, which are described in the Annex and listed at the corresponding page on Snapshot.org. This does not promise any compensation for normal staking/unstaking transactions, or other interactions with the smart contracts.

To source the rewards described above and similar rewards which may be proposed in the future, 100,000 $ZKP shall be allocated out of the total 450M $ZKP allocated for protocol rewards.

Proposed Actions:

1. Approve all parameters included in the sections "Terms for smart contracts" and "Community Deployment Rewards".
2. Authorize and execute on the Ethereum Mainnet and Polygon network the deployment and configuration transactions described in the Annex, to achieve the terms for the AS2 program to be those outlined in the section "Terms for smart contracts",
3. Transfer the reward of 2,000 $ZKP for the front-end v0.5.1 deployment, as per PIP-11's, Proposed actions, Point 1, to the user with the Ethereum address 0xE1B583De9cB37196031b771686734a31ec365768.
4. Allocate 100,000 $ZKP out of the total 450M $ZKP allocated for protocol rewards, to be used for Community Deployment Rewards under the present and future proposals.
5. Request the Panther Foundation to configure the pantherprotocol.eth namespace so that the URL https://ipfs.io/ipns/pantherprotocol.eth will point to the v0.5.3's front-end deployed on IPFS.

Participation:

Please vote to accept or reject the proposed actions detailed above.

As per the existing DAO governance structure, as the staking smart contracts are not currently issuing any rewards, you need to hold $ZKP, staked or not, on the Ethereum Mainnet or Polygon to participate in voting.

Voting power is calculated by Snapshot.org taking a snapshot of the number of ZKP tokens per holder at the block within which the proposal was created.

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-13-extend-advanced-staking-and-ui-updates

and also in raw Markdown format on IPFS, e.g. https://gateway.pinata.cloud/ipfs/QmRa8HbH7JoP1N6hXiXJotNzg72AgEje6xvJZ6iLnnG5Yh?_gl=1

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, and can be independently verified via the snapshot.org web interface.

The complete list of transactions can be found under the following URL: https://docs.pantherprotocol.io/dao/governance/proposal-13-extend-advanced-staking-and-ui-updates/technical-details

Batch 1 transaction 1

Deploy the AdvancedStakeV2ActionMsgTranslator smart contract on the Polygon network by invoking the DeterministicDeploymentProxy on the Polygon Network.

The transaction will initiate a call to FxRoot on the Ethereum mainnet, which will bridge the contract bytecode to the Polygon network through the MaticBridgeModule.

Batch 2 transaction 1

Deploy the AdvancedStakeV2ActionMsgTranslator smart contract on the Ethereum mainnet using the DeterministicDeploymentProxy.

Batch 2 transaction 2..5

Configure the Staking and AdvancedStakeRewardAdviserAndMsgSender smart contracts on the Ethereum mainnet to work with the newly deployed AdvancedStakeV2ActionMsgTranslator.

Batch 2 transaction 6

Re-enable Advanced Stakes on the Ethereum mainnet from Thursday, April 6, 2023, at 6:00:00 PM UTC until Tuesday, August 22, 2023, at 12:00:00 PM UTC, with a lock period of 60 days.

Batch 3

Configure the Staking and AdvancedStakeRewardAdviserAndMsgSender contracts on the Polygon network to interact with the newly deployed AdvancedStakeV2ActionMsgTranslator.

Calls to FxRoot on the Ethereum network will trigger the corresponding calls on the Polygon network.

This is done through the bridging mechanism provided by the MaticBridgeModule.

Once the transactions are executed on the Ethereum network, they will be relayed to the Polygon network, where they will be decoded and executed.

Batch 3 transaction 5

Re-enable advanced stakes on Polygon starting from Thursday, April 6, 2023 at 6:00:00 PM UTC until Tuesday, August 22, 2023 at 12:00:00 PM UTC, with a lock period of 60 days.

The transaction will call FxRoot on the Ethereum mainnet to bridge the configuration data to the Polygon network through MaticBridgeModule.

Batch 3 transaction 6

Update the advanced staking reward parameters by changing the end time to Tuesday, August 22, 2023 at 4:00:00 PM GMT.

The transaction will invoke the call to FxRoot on the mainnet to facilitate the transfer of the configuration call across the Polygon bridge.

Batch 4 transaction 1

Transfer ZKP reward to the community member for executing the PIP-11.

Batch 4 transaction 2..3

Add and configure a 100,000 $ZKP Vesting Pool designated for Community Deployment rewards.