# PIP-37 — Freeze the Advanced Staking v0 Vault and Introduce Merkle-Based Claims

- Space: [Panther Protocol](https://snapshot.box/s:pantherprotocol.eth.md)
- Author: 0xE1B583De9cB37196031b771686734a31ec365768
- State: Closed
- Voting type: Single choice
- Start: 2026-05-25 12:24 UTC
- End: 2026-05-28 12:24 UTC
- Votes: 24
- Quorum: 7,521,798 voting power
- Discussion: https://forum.pantherprotocol.io/t/pip-37-freeze-the-advanced-staking-v0-vault-and-introduce-merkle-based-claims/541
- Open in Snapshot: https://snapshot.box/#/s:pantherprotocol.eth/proposal/0xb2711837bf3b2071390a501d6b9bec703077f927b79ded483aff44844bbe563c

## Results

- For: 7,523,831.97 voting power, 100.0%
- Against: 0 voting power, 0.0%

## Proposal

## 1. Title

### 1.1 Freeze the Advanced Staking v0 Vault and Introduce Merkle-Based Claims

---

## 2. Summary

### 2.1
This proposal authorises the upgrade of the `Vault_Proxy` contract on Polygon to a new implementation named `VaultV0Frozen`.

### 2.2
The upgrade permanently disables the v0 MASP entry and exit paths while introducing a Merkle-tree-based claim mechanism for Advanced Staking reward distributions, including ZKP and PNFT entitlements.

### 2.3
This proposal also introduces a 365-day timelock on any recovery of unclaimed residual assets by the DAO multisig following publication of the final Merkle root.

### 2.4
This proposal contains a single on-chain upgrade action only. The Merkle root authorising claims shall be published and committed through a separate follow-up governance proposal once the entitlement dataset has been finalised.

---

## 3. Background

### 3.1
The Panther v0 MASP environment on Polygon is no longer intended to remain active for ongoing deposit or exit activity.

### 3.2
The DAO intends to transition Advanced Staking reward distribution to a simpler and more transparent Merkle-based claim mechanism while freezing legacy v0 vault interactions.

### 3.3
This proposal finalises the operational state of the v0 Vault by:

(a) disabling further MASP entry and exit interactions;  
(b) preserving reward distribution functionality through Merkle claims; and  
(c) establishing a delayed residual recovery mechanism for unclaimed assets.

---

## 4. Scope of Upgrade

### 4.1
The `Vault_Proxy` contract on Polygon shall be upgraded to the `VaultV0Frozen` implementation.

### 4.2
Following execution of the upgrade:

(a) `PantherPoolV0.exit()` shall revert with `"VFrozen: frozen"`;  
(b) `PantherPoolV0.generateDeposits()` shall revert with `"VFrozen: frozen"`;  
(c) `Vault.lockAsset` and `Vault.unlockAsset` shall revert; and  
(d) no new v0 MASP deposits or exits shall be possible.

### 4.3
At the time of execution, Merkle-based claiming functionality shall not yet be active.

### 4.4
`Vault.claim(...)` shall revert with `"VFrozen: not open"` until a subsequent governance proposal publishes and commits the final Merkle root through `setRoot(bytes32)`.

---

## 5. Merkle Claim Mechanism

### 5.1
Following publication of the Merkle root in a subsequent governance proposal, eligible users may submit claims using the following function:

```solidity
claim(
    uint256 zkpAmount,
    uint16 nftCount,
    bool claimNft,
    bytes32[] proof
)
```

### 5.2
Claimants shall submit their entitlement data together with a valid Merkle proof corresponding to the published root.

### 5.3
Upon successful verification:

(a) the specified ZKP amount shall be transferred to the claimant; and  
(b) where `claimNft = true`, the contract shall distribute the corresponding PNFT allocation.

### 5.4
Claims are single-use only. Any attempt to claim more than once shall revert.

---

## 6. Voting Options

### For
Approve the upgrade of the Polygon `Vault_Proxy` to `VaultV0Frozen`, freeze legacy v0 MASP entry and exit functionality, and prepare the Merkle-based Advanced Staking claims process.

### Against
Do not approve the upgrade and retain the current v0 Vault implementation unchanged.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

