# PIP-13 review, discussion and launch

**URL:** <https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275>\
**Category:** Panther Improvement Proposals (PIPs)\
**Created:** [April 19, 2023, 9:34am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275 "2023-04-19T09:34:04Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joris](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/joris/32/8_2.png) [@Joris](https://forum.pantherprotocol.io/u/Joris)\
**Post date:** [April 19, 2023, 9:34am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/1 "2023-04-19T09:34:05Z")

</div>

Good morning everyone:

We hereby share a proposal to extend the Advanced Staking program, PIP-13! This proposal also covers multiple front-end (UI) updates and the distribution of deployment rewards as stated on [PIP-11](https://snapshot.org/#/pantherprotocol.eth/proposal/0x868231816a6608d4d75cf4bb12f38ceff3228ec2b2f99fca5ec06f865fc4c85a). Please feel free to discuss and review the proposal. If concurred, one of the Snapshot Authors can push it towards Snapshot so that ZKP holders can vote.

---

<div class="post-metadata">

**Author:** ![Joris](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/joris/32/8_2.png) [@Joris](https://forum.pantherprotocol.io/u/Joris)\
**Post date:** [April 19, 2023, 9:36am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/2 "2023-04-19T09:36:51Z")

</div>

# Proposal #13: Extend Advanced Staking and UI Updates

This proposal introduces two key initiatives:

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

1. 
  1. 

Activating updates to the front-end (UI) of Panther Protocol ([version 0.5.1](https://github.com/pantherprotocol/panther-core/releases/tag/v0.5.1)). A list of updates can be found in [the v0.5.3 release description](https://github.com/pantherprotocol/panther-core/releases/tag/v0.5.3).

### 

Background:

1. 
  1. 

The initial “Advanced Staking” program was launched via [PIP-9](https://snapshot.org/#/pantherprotocol.eth/proposal/0x01942f584fe0c27aeef420207135be5ede279998da0a7839f22e2178b2d335ba) and [PIP-10](https://snapshot.org/#/pantherprotocol.eth/proposal/0x0c6f3fd9db866f99d7d0b343687b890cd3240495170f539efcc31f2dc216ebd5) 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.

As discussed on [Panther’s Discourse forum](https://forum.pantherprotocol.io/t/length-of-advanced-staking/130/25), 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](https://snapshot.org/#/pantherprotocol.eth) on [Snapshot.org](http://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.

1. 
  1. 

Through [PIP-11](https://snapshot.org/#/pantherprotocol.eth/proposal/0x868231816a6608d4d75cf4bb12f38ceff3228ec2b2f99fca5ec06f865fc4c85a) Panther’s front-end [v0.5.1](https://github.com/pantherprotocol/panther-core/releases/tag/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](https://github.com/pantherprotocol/panther-core/releases/tag/v0.5.3).

The community recommends using the [v0.5.3](https://github.com/pantherprotocol/panther-core/releases/tag/v0.5.3) front-end instead of [v0.5.1](https://github.com/pantherprotocol/panther-core/releases/tag/v0.5.1) (the previous one).

In order to have a user-friendly URL pointing to [v0.5.3](https://github.com/pantherprotocol/panther-core/releases/tag/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](https://app.ens.domains/name/pantherprotocol.eth) ENS domain namespace in such a way that the user-friendly link [Panther Staking](https://ipfs.io/ipns/pantherprotocol.eth) will point to the [v0.5.3](https://github.com/pantherprotocol/panther-core/releases/tag/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” below 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](https://snapshot.org/#/pantherprotocol.eth/proposal/0x01942f584fe0c27aeef420207135be5ede279998da0a7839f22e2178b2d335ba).

### 

Proposed Actions:

1. 
  1. 

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

1. 
  1. 

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

1. 
  1. 

Transfer the reward of 2,000 $ZKP for the front-end v0.5.1 deployment, as per [PIP-11](https://snapshot.org/#/pantherprotocol.eth/proposal/0x868231816a6608d4d75cf4bb12f38ceff3228ec2b2f99fca5ec06f865fc4c85a)’s, Proposed actions, Point 1, to the user with the Ethereum address 0xE1B583De9cB37196031b771686734a31ec365768.

1. 
  1. 

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.

1. 
  1. 

Request the Panther Foundation to configure the pantherprotocol.eth namespace so that the URL [Panther Staking](https://ipfs.io/ipns/pantherprotocol.eth) will point to the v0.5.3’s front-end deployed on IPFS.

### 

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](http://Snapshot.org), and can be independently verified via the [snapshot.org](http://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​](https://docs.pantherprotocol.io/dao/governance/proposal-13-extend-advanced-staking-and-ui-updates/technical-details%E2%80%8B)

### 

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.

### 

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](http://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 also in raw Markdown format on IPFS, e.g.

---

<div class="post-metadata">

**Author:** ![ToXiC\_eHC](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/toxic_ehc/32/291_2.png) [@ToXiC\_eHC](https://forum.pantherprotocol.io/u/ToXiC_eHC)\
**Post date:** [April 19, 2023, 9:50am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/3 "2023-04-19T09:50:26Z")

</div>

Looks great looking forward to voting on this one!

---

<div class="post-metadata">

**Author:** ![MoonRocket](https://avatars.discourse-cdn.com/v4/letter/m/ee59a6/32.png) [@MoonRocket](https://forum.pantherprotocol.io/u/MoonRocket)\
**Post date:** [April 19, 2023, 10:00am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/4 "2023-04-19T10:00:30Z")

</div>

Lookinng forward to stack my ZKP again 🙏

---

<div class="post-metadata">

**Author:** ![M-M](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/m-m/32/70_2.png) [@M-M](https://forum.pantherprotocol.io/u/M-M)\
**Post date:** [April 19, 2023, 10:01am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/5 "2023-04-19T10:01:43Z")

</div>

An adequate PIP, I agree with it.

---

<div class="post-metadata">

**Author:** ![Ron](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/ron/32/49_2.png) [@Ron](https://forum.pantherprotocol.io/u/Ron)\
**Post date:** [April 19, 2023, 10:08am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/6 "2023-04-19T10:08:47Z")

</div>

Lets vote today… looks good

---

<div class="post-metadata">

**Author:** ![DanP](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/danp/32/79_2.png) [@DanP](https://forum.pantherprotocol.io/u/DanP)\
**Post date:** [April 19, 2023, 10:14am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/7 "2023-04-19T10:14:44Z")

</div>

What happens with the left over ZKP if there is an excess at the end of staking/V1 implementation

---

<div class="post-metadata">

**Author:** ![Zilius](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/zilius/32/181_2.png) [@Zilius](https://forum.pantherprotocol.io/u/Zilius)\
**Post date:** [April 19, 2023, 10:23am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/8 "2023-04-19T10:23:43Z")

</div>

great, we’ve all been waiting for this for a long time, let’s start voting as soon as possible, I support

---

<div class="post-metadata">

**Author:** ![Elysion](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/elysion/32/159_2.png) [@Elysion](https://forum.pantherprotocol.io/u/Elysion)\
**Post date:** [April 19, 2023, 10:31am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/9 "2023-04-19T10:31:36Z")

</div>

Great news, I fully support this, let’s go!

---

<div class="post-metadata">

**Author:** ![Av8R](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/av8r/32/23_2.png) [@Av8R](https://forum.pantherprotocol.io/u/Av8R)\
**Post date:** [April 19, 2023, 10:54am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/10 "2023-04-19T10:54:30Z")

</div>

Looking forward to the voting! Great proposal!

---

<div class="post-metadata">

**Author:** ![Scott\_W](https://avatars.discourse-cdn.com/v4/letter/s/48db29/32.png) [@Scott\_W](https://forum.pantherprotocol.io/u/Scott_W)\
**Post date:** [April 19, 2023, 12:02pm UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/11 "2023-04-19T12:02:09Z")

</div>

Great proposal - looking forward to the visual updates!

---

<div class="post-metadata">

**Author:** ![Praetorian](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/praetorian/32/69_2.png) [@Praetorian](https://forum.pantherprotocol.io/u/Praetorian)\
**Post date:** [April 19, 2023, 12:33pm UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/12 "2023-04-19T12:33:24Z")

</div>

Looks good, Lets Vote

---

<div class="post-metadata">

**Author:** ![SolidSnak3](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/solidsnak3/32/111_2.png) [@SolidSnak3](https://forum.pantherprotocol.io/u/SolidSnak3)\
**Post date:** [April 19, 2023, 1:22pm UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/13 "2023-04-19T13:22:16Z")

</div>

Looks good! Want to get mine staked ASAP

---

<div class="post-metadata">

**Author:** ![Noynie](https://avatars.discourse-cdn.com/v4/letter/n/ecb155/32.png) [@Noynie](https://forum.pantherprotocol.io/u/Noynie)\
**Post date:** [April 19, 2023, 4:51pm UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/14 "2023-04-19T16:51:02Z")

</div>

I agree with the proposal. Let’s take it to a vote ASAP.

---

<div class="post-metadata">

**Author:** ![Akin](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/akin/32/139_2.png) [@Akin](https://forum.pantherprotocol.io/u/Akin)\
**Post date:** [April 19, 2023, 6:33pm UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/15 "2023-04-19T18:33:45Z")

</div>

Let’s go ahead. Support it to move forward.

---

<div class="post-metadata">

**Author:** ![Lom1985](https://avatars.discourse-cdn.com/v4/letter/l/f4b2a3/32.png) [@Lom1985](https://forum.pantherprotocol.io/u/Lom1985)\
**Post date:** [April 19, 2023, 7:35pm UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/16 "2023-04-19T19:35:46Z")

</div>

It looks great. Let’s goo!

---

<div class="post-metadata">

**Author:** ![ToXiC\_eHC](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/toxic_ehc/32/291_2.png) [@ToXiC\_eHC](https://forum.pantherprotocol.io/u/ToXiC_eHC)\
**Post date:** [April 19, 2023, 8:09pm UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/17 "2023-04-19T20:09:27Z")

</div>

It is live now - this is the link on snapshot:  
[https://snapshot.org/#/pantherprotocol.eth/proposal/0x0825de3b9289d3e04e8f9f3607d1145923f482104fecabc9d02634b3f7d6f521](https://snapshot.org/#/pantherprotocol.eth/proposal/0x0825de3b9289d3e04e8f9f3607d1145923f482104fecabc9d02634b3f7d6f521)

---

<div class="post-metadata">

**Author:** ![ToXiC\_eHC](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/toxic_ehc/32/291_2.png) [@ToXiC\_eHC](https://forum.pantherprotocol.io/u/ToXiC_eHC)\
**Post date:** [April 23, 2023, 4:02am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/18 "2023-04-23T04:02:04Z")

</div>

![7j3cbk](https://canada1.discourse-cdn.com/flex036/uploads/pantherprotocol/original/1X/a8ec7b8f3acf09353cc0f76534c8f90505b85fbe.gif)

---

<div class="post-metadata">

**Author:** ![Joris](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/joris/32/8_2.png) [@Joris](https://forum.pantherprotocol.io/u/Joris)\
**Post date:** [April 24, 2023, 10:47am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/20 "2023-04-24T10:47:57Z")

</div>

During the first Advanced Staking program, approximately 44% of the reward pool has been claimed. Since this new program has a similar duration and APR rate, if a comparable amount of $ZKP has been staked, I think it’s safe to say that approximately 88% being claimed at the end of the program (120 days) is to be likely.

The other 12% could for example be reserved for testnet rewards, allocated for mainnet (V1.0), and so forth.

---

<div class="post-metadata">

**Author:** ![DanP](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/danp/32/79_2.png) [@DanP](https://forum.pantherprotocol.io/u/DanP)\
**Post date:** [April 24, 2023, 11:00am UTC](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275/21 "2023-04-24T11:00:40Z")

</div>

Sounds good to me 👍🏻

[Next page](https://forum.pantherprotocol.io/t/pip-13-review-discussion-and-launch/275.md?page=2)
