# PIP-41: Restore Base V1 Deployment and Initiate Ethereum Deployment

- Space: [Panther Protocol](https://snapshot.box/s:pantherprotocol.eth.md)
- Author: 0xE1B583De9cB37196031b771686734a31ec365768
- State: Closed
- Voting type: Single choice
- Start: 2026-08-17 11:46 UTC
- End: 2026-08-20 11:46 UTC
- Votes: 21
- Quorum: 7,521,798 voting power
- Discussion: https://forum.pantherprotocol.io/t/pip-41-restore-base-v1-deployment-and-initiate-ethereum-deployment/550
- Open in Snapshot: https://snapshot.box/#/s:pantherprotocol.eth/proposal/0x8e7efd14e240faf6755d72af437f392f8200b7a55c903e54dcef8716d5f346f7

## Results

- For: 8,354,249.73 voting power, 100.0%
- Against: 0 voting power, 0.0%

## Proposal

**PIP-41: Restore Base V1 Deployment, Initiate Ethereum Deployment and Compliance Role Funding**

**Proposal Summary**

This proposal seeks governance approval to:

* Restore the required **ZKP balances** to the Base V1 deployment using ZKP minted from the **rewards pool**.
* Restore the non-ZKP test asset balances required by VaultV1 to support withdrawals on Base.
* Use **DAO Council operational funding** to acquire the required non-ZKP assets.
* Initiate the build and deployment process for Panther V1 on **Ethereum**.
* Authorize the **Compliance Role funding** to be handled via DAO Grants.

---

**Motivation**

**1. Restore Base V1 ZKP balances**

To restore the Base V1 deployment to its required operational state, ZKP balances must be returned to three contracts:

* ZkpReserveController: **3,840,888.4 ZKP**
* VaultV1: **1,000,546.507790072217357505 ZKP**
* PantherPoolV1: **280,766.6906 ZKP**

This represents an exact requirement of **5,122,201.598390072217357505 ZKP**.

The required ZKP will be **minted from the rewards pool** and distributed to the respective Base V1 contracts.

**2. Restore VaultV1 test assets**

VaultV1 also requires the other test assets used by the Base deployment to be restored. Without sufficient balances of these assets in the vault, withdrawals of the corresponding tokens will revert.

The following assets are required:

* **0.000119127498140994 WETH**
* **0.434819 USDC**
* **0.100842079824413618 AERO**
* **0.066781363580384114 VIRTUAL**
* **0.018154422481002229 MORPHO**
* **0.000335444255711905 AAVE**
* **5.49509528069306407 ZORA**
* **0.00000325 cbBTC**

These assets will be acquired using **DAO Council operational funding** and transferred to VaultV1 on Base.

**3. Initiate Panther V1 deployment on Ethereum**

This proposal also seeks approval to begin the build and deployment process for **Panther V1 on Ethereum**.

The Ethereum deployment will extend the V1 architecture to Ethereum and begin the technical work required to prepare the deployment for testing and subsequent launch.

Approval of this proposal authorizes the development team to begin the necessary build, configuration, integration, testing, and deployment preparation work for Ethereum.

Exact details regarding **contract addresses, token and reward parameters, limits, token whitelist, and rewards and subsidies minting** will be prepared and presented in the next PIP.

**4. DAO Council management of Compliance Role funding**

This proposal seeks authorization for the DAO Council to manage the monthly funding of the **Compliance Role via DAO Grants**.

The DAO Council treasury has exhausted its ZKP reserves allocated for the Compliance Role. This proposal will therefore authorize DAO Grants to cover the ongoing Compliance Role costs, maintaining the intent of the funding arrangement originally approved under **PIP-24**.

---

**Proposed Changes**

**1. Restore ZKP to Base V1**

Mint **5,122,201.598391 ZKP from the rewards pool**.

The required Base balances are:

* ZkpReserveController — **3,840,888.4 ZKP**
* VaultV1 — **1,000,546.507790072217357505 ZKP**
* PantherPoolV1 — **280,766.6906 ZKP**

The exact requirement is **5,122,201.598390072217357505 ZKP**. Due to the precision supported by VestingPools, the mint is rounded up to **5,122,201.598391 ZKP**, resulting in a surplus of **927782642495 wei**.

**2. Restore non-ZKP assets to VaultV1**

Using **DAO Council operational funding**, acquire and transfer the following assets to VaultV1 on Base:

* WETH — 0.000119127498140994
* USDC — 0.434819
* AERO — 0.100842079824413618
* VIRTUAL — 0.066781363580384114
* MORPHO — 0.018154422481002229
* AAVE — 0.000335444255711905
* ZORA — 5.49509528069306407
* cbBTC — 0.00000325

These balances are required to ensure withdrawals of the corresponding assets can be processed successfully by VaultV1.

**3. Begin Ethereum deployment**

Authorize the development team to initiate the **Panther V1 Ethereum deployment**, including:

* Preparing and configuring the V1 contracts for Ethereum.
* Building and configuring the required deployment infrastructure.
* Performing integration and deployment testing.
* Preparing the Ethereum deployment for subsequent launch and governance actions where required.

Exact details regarding **contract addresses, token and reward parameters, limits, token whitelist, and rewards and subsidies minting** will be prepared and presented in the next PIP.

**4. DAO Council manages Compliance Role funding**

Authorize the DAO Council to manage the **Compliance Role monthly funding via DAO Grants**.

This will allow DAO Grants to cover the ongoing Compliance Role costs while maintaining the intent of the arrangement originally approved under **PIP-24**.

---

**Next Steps**

**Base restoration**

Following approval:

1. Mint the required **ZKP from the rewards pool**.
2. Transfer the required ZKP to the Ethereum DAO Multisig.
3. Bridge the required ZKP to Base.
4. Distribute the ZKP to ZkpReserveController, VaultV1, and PantherPoolV1.
5. Acquire the required non-ZKP assets using **DAO Council operational funding**.
6. Transfer the acquired assets to VaultV1.
7. Verify the restored balances and test Base V1 deposit and withdrawal functionality.

**Ethereum deployment**

Following approval, the development team may begin the technical build and deployment process for Panther V1 on Ethereum.

The Ethereum deployment will proceed through the required development, testing, compliance, and governance stages before being made available to users.

Exact details regarding **contract addresses, token and reward parameters, limits, token whitelist, and rewards and subsidies minting** will be prepared and presented in the next PIP.

**Compliance Role funding**

Following approval, the DAO Council will be authorized to use **DAO Grants to fund the Compliance Role**, consistent with the intent of PIP-24.

---

**Voting**

**PIP-41** will be published on Snapshot for a **3-day vote**, with voting eligibility defined in **PIP-7**.

---

**Transactions for the Snapshot**

**PIP-41: Mint 5,122,201.598391 ZKP to the Ethereum DAO Multisig to restore the Base V1 deployment**

**Addresses**

Panther contracts on Ethereum:

* DAO Multisig: `0x505796f5Bc290269D2522cf19135aD7Aa60dfd77`
* VestingPools: `0xb476104aa9D1f30180a01987FB09b1e96dDCF14B`
* ZKP: `0x909E34d3f6124C324ac83DccA84b74398a6fa173`

**Transaction Overview**

The Base V1 deployment was drained on 2026-08-06 through a compromised Reality.eth Zodiac module on the Base Safe. The contract implementations have been restored; these transactions replace the required ZKP.

A total of **5,122,201.598391 ZKP** will be minted to the Ethereum DAO Multisig. Bridging to Base and subsequent distribution to the Base V1 contracts will be performed manually afterwards and are not part of the Snapshot transactions.

Existing vesting pool #18 has **57,155 ZKP** remaining and available for release. A new vesting pool #25 will therefore provide the remaining **5,065,046.598391 ZKP**.

**Important:** Transaction #1 must execute before **2026-08-31**, otherwise it will revert because the configured pool start date would be in the past.

All four transactions are signed by the Ethereum DAO Multisig.

**Ethereum Direct Actions — 4 Transactions**

**Transaction #1 — addVestingPools**

Create vesting pool #25 for **5,065,046.598391 ZKP**, assigned to the Ethereum DAO Multisig.

* Start: 2026-08-31
* Vesting period: 1 day
* Adjustable: Yes
* Pre-minted: No
* Contract: VestingPools

**Transaction #2 — updatePoolTime**

Move vesting pool #25's start date to **2026-08-01**, allowing the full allocation to become releasable.

* Pool: #25
* New start: 2026-08-01
* Vesting period: 1 day
* Contract: VestingPools

**Transaction #3 — releaseTo**

Release **5,065,046.598391 ZKP** from vesting pool #25 to the Ethereum DAO Multisig.

* Pool: #25
* Recipient: Ethereum DAO Multisig
* Amount: 5,065,046.598391 ZKP
* Contract: VestingPools

**Transaction #4 — releaseTo**

Release the remaining **57,155 ZKP** from existing vesting pool #18 to the Ethereum DAO Multisig.

* Pool: #18
* Recipient: Ethereum DAO Multisig
* Amount: 57,155 ZKP
* Contract: VestingPools

The executable calldata for these four actions will be included directly in the corresponding Snapshot transactions.

---

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

