Extending Advanced Staking

I see no reason to change any parameters. If it ain’t broke, don’t fix it - sort of thing :rofl:

Quite pleased with advanced staking so far. Looking forward to realising my rewards with the launch of V1!

4 Likes

Hi all,

Ditto on Dan’s point - I don’t think we really need to change it up at this stage

lets just wait for new proposal i agree with not changing apr and zkp for execution

Since we discovered today v0.53 staking only allocates rewards up to the end of staking while still locking for 60 days I would say it’s very important that a 60 day locked stake on day 1 or day 60 gives a 60 days reward.

1 Like

Hey guys, we’ve been discussing this and created a proposal similar to the last one (with new terms for this to be a third term of Advanced Staking). I’m dropping it below for y’all to discuss:


PIP-16: Extend Advanced Staking

Summary:

This proposal introduces the initiative of extending the “Advanced Staking” program for another two months, with stakes to be accepted till October 22, 2023 and rewards to be accrued at the APR of 15% for the locking period of 60 days.

Therefore, the new staking cycle to be started with parameters stated in the “Terms for smart contracts” section.

Background:

The initial “Advanced Staking” program was launched via PIP-9, PIP-10, and prolonged via PIP-13. The extended Advanced Staking program is valid till August 22, 2023 and the corresponding rewards are to be calculated for the same period.

The community proposes to launch the new cycle (“program”) prior the completion of the previous program (activated via PIP-13) that will be stopped simultaneously with the start of the new one.

The remaining $ZKP tokens originally allocated as staking rewards according to proposals PIP-9 shall be used to source rewards under the new program.

As discussed on Panther’s Discourse forum, the community recommends running a new cycle of the “Advanced Staking” program (AS3), with parameters stated below in the “Terms for smart contracts” section.

This proposal (1) authorizes updates of the current UI which introduce the new staking terms as described below, (2) autorizes 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 AS3.

Terms for smart contracts:

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

Parameter Description
First day stakes are accepted As soon as relevant PIP is passed and executed.
Last day stakes are accepted October 22, 2023, 12:00 am UTC, or earlier if “Amount of $ZKP allocated for rewards to all stakers” below has been already depleted, or earlier if Panther’s v1 is launched beforehand.
Amount of $ZKP allocated for rewards to all stakers The remaining part of rewards, which were allocated according to PIP-9 and used during two cycles of the Advanced Staking program.
Number of days the staked $ZKP remains locked after stake creation 60 days
Reward formula, where: Reward - reward for a stake ($zZKP) Amount - amount staked ($ZKP)APR - Annual Percentage Rate (%) Period - rewarded period (days) Reward = AmountAPRPeriod / 365

APR - 15%,
Period - 60 days|
|Minimum $ZKP amount per stake|1000|
|Time since when a staker might withdraw rewards from the MASP (but forfeiting the right to accumulate PRPs|Immediately after the stake is created.|

Community Deployment Rewards:

Users who execute blockchain transactions listed in the Annex shall be rewarded as follows:

  1. 2,000 $ZKP shall be rewarded to the first deployer of the updated UI to IPFS.
  2. 3,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 3 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.

Proposed Actions:

  1. Approve all parameters included in the sections “Terms for smart contracts” and “Community Deployment Rewards”.
  2. Authorize UI code updates to implement new terms,
  3. 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 AS3 program to be those outlined in the section “Terms for smart contracts”,
  4. Request the Panther Foundation to configure the pantherprotocol.eth namespace so that the URL Panther Staking will point to the updated UI 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.

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.

Batch 1 transaction 1

Deploy the AdvancedStakeV3ActionMsgTranslator 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 AdvancedStakeV3ActionMsgTranslator smart contract on the Ethereum mainnet using the DeterministicDeploymentProxy.

Batch 2 transaction 2…5

Configure the Staking and RewardMaster smart contracts on the Ethereum mainnet to work with the newly deployed AdvancedStakeV3ActionMsgTranslator.

Batch 2 transaction 6

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

Batch 3 transactions 1…4

Configure the Staking and RewardMaster contracts on the Polygon network to interact with the newly deployed AdvancedStakeV3ActionMsgTranslator.

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.

Batch 3 transaction 5

Re-enable advanced stakes on Polygon starting from Thursday, August 22, 2023, at 12:00:00 PM UTC until Sunday, October 22, 2023 at 12:00:00 AM 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 Thursday, December 21, 2023 12:00:00 AM UTC.

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

Great job… I will support it.

Despite reaching a vote of 11 million the quorum did not pass the required 12.1 million votes.

Since there is now no active staking program, snapshot needs to be updated to allow anyone holding ZKP staked or unstaked to vote.

I suggest we put this forward to a new vote as such.

Hello friends it is time to address extending advanced staking again since it is expiring end of October 2023 again.

We need to allocate more rewards to the pool and I personally would like to see the APR increased for these final rounds to reward the people who have remained committed to the program.

image

2 Likes

I agree that in order to retain loyal holders, it is necessary to definitely increase the APR

Great lets see by Poll what rate people want:

  • No Change 15% APR
  • Double Down 30% APR
  • Trifeca 45% APR
  • Big BULL 60% APR
  • Year End SALE 100% APR
0 voters
1 Like

We have to make sure that we arnt raising it so high that the bigger bag holders don’t scoop up the whole lot before the staking period is over I think we should deffinalty aim to drain the pool but also make sure that everyone gets the whole period of rewards.

Also just to bring it to mind we don’t know if we will want another staking period after this next one depending on how long V1 development is if we drain the pool in this last go we might have nothing to do for a month or two and that feels bad.

Towel - obviously we would increase the reward pool to match - we know we got +/- 93 million staked so we have an idea of what type of reward pool would be needed for the APR allocated.
Also obviously once V1 is live this falls away/stops.

1 Like

Dear community,

We hereby share a proposal draft to extend the Advanced Staking program, PIP-19! Furthermore this proposal introduces additional UI updates, and the distribution of the deployment rewards in $ZKP. Check it out and let your voice be heard!

2 Likes

PIP-19: Extend Advanced Staking

Summary:

This proposal extends the “Advanced Staking” program for another four months, with stakes accepted till March 10, 2024 and rewards accrued at an APR of 15% (same as prior period) with the locking period of 60 days.

The new staking cycle will be started with the parameters stated in the “Terms for smart contracts” section.

Background:

The initial “Advanced Staking” program was launched via PIP-9, PIP-10, and prolonged via PIP-13 and PIP-18. The extended Advanced Staking program was valid till October 28, 2023 and the corresponding rewards were calculated for the same period.

The community proposes to launch the new cycle (“program”) given the completion of the previous program (activated via PIP-18). As discussed on Panther’s Discourse forum, the community recommends running a new cycle of the “Advanced Staking” program (AS4), with the parameters stated below in the “Terms for smart contracts” section.

The remaining $ZKP tokens originally allocated as staking rewards according to proposal PIP-9 shall be used to source rewards under the new program.

This proposal (1) authorizes updates to the current UI which introduce the new staking terms as described below, (2) autorizes 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 Advance Staking - 4 (AS4).

Terms for smart contracts:

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

Parameter Description
First day stakes are accepted As soon as the PIP is passed and executed.
Last day stakes are accepted March 10, 2024, 12:00 am UTC, or earlier if “Amount of $ZKP allocated for rewards to all stakers” below has been already depleted, or earlier if Panther’s v1 is launched beforehand.
Amount of $ZKP allocated for rewards to all stakers 1) The remaining part of rewards, which were allocated according to PIP-9 and used during three cycles of the Advanced Staking program.
  1. The additional $ZKP 2M, which are the tokens recovered by the Polygon bug fix PIP.|
    |Number of days the staked $ZKP remains locked after stake creation|60 days|
    |Reward formula, where: Reward - reward for a stake ($zZKP) Amount - amount staked ($ZKP) APR - Annual Percentage Rate (%) Period - rewarded period (days)|Reward = AmountAPRPeriod / 365,
    APR - 15%,
    Period - 60 days|
    |Minimum $ZKP amount per stake|1000|
    |Time since for a staker to withdraw rewards from the MASP (but forfeiting the right to accumulate PRPs)|Immediately after the stake is created.|

Community Deployment Rewards:

Users who execute blockchain transactions listed in the Annex shall be rewarded as follows:

  1. 2,000 $ZKP shall be rewarded to the first deployer of the updated UI to IPFS.
  2. 3,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 3 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 on the corresponding page on Snapshot.org. This does not promise any compensation for normal staking/unstaking transactions, or other interactions with the smart contracts.

Proposed Actions:

  1. Approve all parameters included in the sections “Terms for smart contracts” and “Community Deployment Rewards”.

  2. Authorize UI code updates to implement new terms,

  3. 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 AS4 program to be those outlined in the section “Terms for smart contracts”, including the adding funds to the rewards pool.

  4. Send the deployment rewards according to the points 1, 2 and 3 of the ‘‘Community Deployment Rewards’’ section of PIP-18, namely:

  5. The distribution of 2000 $ZKP towards the following address for deploying the updated front-end (v0.5.4) onto IPFS:0xE1B583De9cB37196031b771686734a31ec365768

  6. 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

  7. The distribution of $146 USD in $ZKP tokens - which is $ZKP 7685 at the rate $ZKP=0.019 USD - as a gas fee compensation for the community member who executed point 3 of the Proposed Actions section, PIP-18: :0xE1B583De9cB37196031b771686734a31ec365768

  8. Request the Panther Foundation to configure the pantherprotocol.eth namespace so that the URL Panther Staking will point to the updated UI deployed on IPFS.

Acceptance Criteria:

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!”,

“lang”: “en”,

“type”: “bool”,

“category”: “DAO proposal”

}

Reality.eth should resolve the question to “yes” only for proposals that:

  • were initiated as a Snapshot proposal in the PantherProtocol.eth space (athttps://snapshot.org/#/pantherprotocol.eth);
  • 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, 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”.

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.

2 Likes

This looks good to me, I think we should proceed.

I will support this PIP, however, I do find that 15% is a little underwhelming, based on the outcome of the community poll above, and given the community’s resilience and perseverance over the last two years in anticipation of the V1 product.

4 Likes

Sorry if I misunderstood…but just wanted to confirm that we will continue to acquire rewards at a 15% apr till March 2024 as per PIP-19 proposal?

Got my vote too! How one can be first to deploy on IPFS and proof it, curious about it. Hosting it on IPFS since long btw.

How one can execute tx to deploy contracts?

edit:
Talking about IPFS, the ENS pantherprotocol.eth is redirecting to this IPFS hash below which seems to be the UI first or second version:
bafybeicfwkwxy7g27x2rgiaa5f5bv5rupfxablc4ngqftptpns2dlpk6pm

The actual v5 IPFS hash is the one below:
bafybeief75kkgrtzsfmsnkhd3fsfrw5rjngraakbzub3dhczhdzp2uydr4

That is without using IPNS link and through pantherprotol.eth. When using the IPNS link like Panther Staking, it display the actual UI.

Hello, this is what I understand too. Could be before if the amount left allocated to the reward pool is depleted before or if the v1 is live on mainnet before.

1 Like

As long as you restake every 60 days and as long as there are rewards left in the reward pool yes.

1 Like