# PIP-42: Launch of DAO-Operated Zone on Base, Ownership Transition & Compliance Changes

- Space: [Panther Protocol](https://snapshot.box/s:pantherprotocol.eth.md)
- Author: 0xE1B583De9cB37196031b771686734a31ec365768
- State: Closed
- Voting type: Single choice
- Start: 2026-09-10 10:30 UTC
- End: 2026-09-13 10:30 UTC
- Votes: 15
- Quorum: 7,521,798 voting power
- Open in Snapshot: https://snapshot.box/#/s:pantherprotocol.eth/proposal/0xbc5928b504356a9a8514513f59beb62fda7a59854960e7040991d9b0eb74af47

## Results

- For: 8,263,853.72 voting power, 100.0%
- Against: 0 voting power, 0.0%

## Proposal

**Summary**

This proposal:

1. Formally launches the DAO-operated Zone on Base upon confirmed completion and execution of all transactions and scripts required for the transition of ownership.

2. Completes the transition of the ownerSafeDao Safe on Base to full DAO control by removing the two remaining legacy individual signers and leaving the Ethereum DAO signers in control.

3. Raises the ZkpReserveController emission rate to approximately **16,000 ZKP per day** on Base.

4. Confirms the risk logic used when handling high-risk users for internal transfers and withdrawals.

5. Clarifies the Compliance Role funding arrangement established under PIP-41.

Together, these actions complete the Base launch and confirm the updated governance and compliance standards.

---

**Motivation**

Panther has been working towards the Base launch for some time, and these final actions bring that work to fruition.

For the launch to be successful, ownership of the relevant contracts must be under DAO control, consistent with the governance approach used on Polygon. Following this transition, future changes to the DAO-controlled deployment will require governance approval through subsequent PIPs.

To support internal transfers safely, this proposal also confirms the compliance logic designed to protect users against bad actors while preserving user sovereignty over their own funds.

Finally, this proposal clarifies a funding detail stated in PIP-41 so that no further ZKP minting is required to fund the Compliance Role.

Removing the legacy signers:

* Aligns control with DAO governance.
* Reduces operational risk.
* Simplifies key management.
* Strengthens decentralisation.
* Finalises the governance structure ahead of launch.

---

**Compliance Flow Rationale**

Panther's compliance logic is designed around a core principle: no user should have their funds trapped or effectively frozen within the protocol solely because of their risk classification.

This follows the approach taken by other privacy-preserving protocols, such as Privacy Pools, where users retain the ability to recover their own funds while controls prevent potentially illicit funds from being transferred to other users.

In line with this principle:

* High-risk or sanctioned users are restricted from sending funds to other users, whether through an internal transfer or withdrawal to a third-party wallet.

* All users, regardless of risk classification, retain the ability to withdraw their own funds back to their own wallet.

* The restriction is enforced automatically through smart contract logic and requires no discretionary action, case review, or manual authorisation by the Compliance Officer or another party.

* Panther DAO cannot intercept, reverse or freeze a transaction, and users retain the ability to exit the protocol to their own wallet.

---

**Compliance Risk Flow**

* **No-risk and low-risk users:** May interact freely with all protocol functions.

* **High-risk or sanctioned users:** Cannot send funds to other users through internal transfers or withdrawals to third-party wallets.

* **Withdrawals to own wallet:** All users may withdraw to their own wallet regardless of risk classification.

* **Enforcement:** The entire flow is automated and requires no Compliance Officer action, review or discretion.

---

**The Changes Made**

**1. Launch the DAO-operated Zone on Base**

The DAO-operated Zone on Base becomes the official live operational environment of Panther Protocol under DAO control.

Upon confirmation, the DAO Multisig:

* Formally declares the Zone live.
* Activates the production interface.
* Recognises the Base deployment as the official DAO-operated environment.

**2. Complete Safe ownership transition**

Remove the following two legacy signers from the Base Safe:

* Signer 1: `0xb83A3094272B6425f89BB5590b48928e2374eE11`
* Signer 2: `0xFee6D2Cb5816282D853fba79cB9C8b5EDB7908Cd`

Following their removal, the Safe remains controlled by the **five Ethereum DAO signers with a 2-of-5 threshold**.

**3. Raise Base ZKP reward emission**

Update the Base ZkpReserveController emission rate to:

`370370000000000000 wei/block`

This corresponds to approximately **16,000 ZKP per day on Base**.

The existing `minRewardedAmount` remains unchanged.

**4. Confirm compliance logic**

Confirm the compliance risk flow described above as the operational standard for internal transfers and withdrawals on the DAO-operated Base deployment.

---

**Compliance Grant Funding**

PIP-24 established the Compliance Officer's compensation at an agreed hourly rate.

PIP-41 subsequently authorized the DAO Council to use DAO Grants to fund the Compliance Role, consistent with the intent of PIP-24. However, the wording did not clearly distinguish between maintaining the agreed compensation rate and continuing payment specifically in ZKP.

This proposal clarifies that arrangement.

The Compliance Officer's compensation will continue at the hourly rate agreed under **PIP-24**, but will be settled in **USDT/USDC rather than ZKP**, sourced from DAO Council Grants.

This removes the need to mint additional ZKP to fund the Compliance Role while preserving the compensation arrangement previously approved by governance.

---

**Execution**

The governance execution takes place directly on **Base via the Reality module**, with no Ethereum-to-Base bridge transaction required for these actions.

The Reality module must be enabled on the Safe before execution.

Three Base transactions are required:

1. Remove legacy Signer 1 from the Base Safe.
2. Remove legacy Signer 2 from the Base Safe.
3. Update the ZkpReserveController emission rate to approximately 16,000 ZKP/day.

These calls are bundled into the governance execution batch.

---

**Voting**

**For**

Confirm the launch of the DAO-operated Zone on Base, execute the Safe ownership transition, raise the Base ZKP reward emission, approve the compliance standards described above, and approve the Compliance Role funding clarification.

**Against**

Do not launch the DAO-operated Zone on Base and make no changes to Safe ownership, ZKP reward emission, or compliance/funding policy at this time.

---

**Transactions for the Snapshot**

**PIP-42: Remove the Two Legacy Signers from the Base Safe and Raise the ZkpReserveController Emission**

**Addresses**

Panther contracts on Base:

* Safe: `0xb16283A233D5b010A7b290d593847207495F0284`
* RealityModule: `0x4ce69e77A8806B51f15b8D0FC38A9c1f66A851b4`
* Reality.eth: `0x2F39f464d16402Ca3D8527dA89617b73DE2F60e8`
* ZkpReserveController: `0xEEA28cf0837306041FA53187F0802aC95228CD45`

**Transaction Overview**

This execution removes the two remaining legacy signers from the Base Safe, leaving the five Ethereum DAO signers operating with a **2-of-5 threshold**.

It also raises the ZkpReserveController emission rate to `370370000000000000 wei/block`, corresponding to approximately **16,000 ZKP/day on Base**.

The existing `minRewardedAmount` remains unchanged.

Execution occurs directly on Base through the **Reality module**. No bridge is required.

**Important:** The Reality module must be enabled on the Base Safe before these transactions are executed.

All three actions form part of the Base governance execution batch.

**Base Direct Actions — 3 Transactions**

**Transaction #1 — removeOwner**

Remove legacy signer:

`0xb83A3094272B6425f89BB5590b48928e2374eE11`

* Safe: `0xb16283A233D5b010A7b290d593847207495F0284`
* Previous owner: `0xeF5795C6a59549100afBFDC209BE63ED85E6a402`
* Threshold after removal: **2**
* Method: `removeOwner(address,address,uint256)`

**Transaction #2 — removeOwner**

Remove legacy signer:

`0xFee6D2Cb5816282D853fba79cB9C8b5EDB7908Cd`

* Safe: `0xb16283A233D5b010A7b290d593847207495F0284`
* Previous owner: `0xeF5795C6a59549100afBFDC209BE63ED85E6a402`
* Threshold after removal: **2**
* Method: `removeOwner(address,address,uint256)`

**Transaction #3 — updateParams**

Set the ZkpReserveController emission rate to:

`370370000000000000 wei/block`

Approximately **16,000 ZKP/day on Base**.

* ZkpReserveController: `0xEEA28cf0837306041FA53187F0802aC95228CD45`
* New emission: `370370000000000000`
* minRewardedAmount: `20000000000000000000000` (unchanged)
* Method: `updateParams(uint256,uint256)`

The executable calldata for these three 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

