09 / PRIVACY / DAO-GRANT DEPLOYMENT

Panther.

Privacy protocol for public chains. Zpoken carried Panther Protocol's deployment to Base under a DAO-approved grant — accepted unanimously — with dApp work ongoing.

engagementDAO grant · deployment
networkBase
stateLive · ongoing
period2025–2026

§1 — The brief.

The brief.

Panther Protocol is a privacy protocol for public chains — shielded pools with compliance rails, live on Polygon. The DAO wanted Panther on Base. Deploying a privacy protocol to a new network is not a redeploy-and-hope exercise: pool contracts, cryptographic and economic parameters, compliance integrations, and the dApp all have to arrive intact, verifiable, and governable by the DAO that owns them — not by the contractor who shipped them.

§2 — What we shipped.

What we shipped.

[01]
Base deployment enablement — configs, deployment and verification scripts, runbook, parameter templates
─ DELIVERED
[02]
PantherPoolV1 on Base — deployed December 2025, source-verified, activated by DAO vote
─ LIVE
[03]
dApp work — Base functionality
─ ONGOING
[04]
Core repository
─ PUBLIC

The engagement ran through Panther's own governance, end to end: Zpoken's grant proposal was accepted by PantherDAO unanimously — PIP-29, November 2025, 9.5M ZKP for, zero against — and the deployment was activated by a second unanimous vote (PIP-30, January 2026). Panther's blog names Zpoken a development partner; the DAO's monthly dev planning tracks the work in the open.

§3 — Engineering decisions.

Engineering decisions.

A deployment the DAO owns, not a ceremony it watched.

Everything needed to control the deployment — configs, scripts, verification, runbook, parameter templates — was delivered open-source. The DAO, not the contractor, holds the ability to audit, reproduce, and redeploy.

Mainnet rules, network-appropriate whitelist.

Per the accepted proposal, Base runs the same cryptographic, economic, and compliance parameters live on Polygon; only the token whitelist was adapted to the network — nine assets, verified on Basescan before the activation vote.

Governance-first sequencing.

Proposal → unanimous acceptance → deployment → source verification → separate activation vote. The chain of custody is public at every step: the forum thread, two Snapshot votes, and a verified contract.

§4 — Where it stands.

Where it stands.

Live and ongoing. PantherPoolV1 was deployed to Base in December 2025 and has been live since its January 2026 activation; dApp work and deployment support continue — the DAO's own dev planning reads "Supporting ZPOKEN on Base Deployment."

§5 — Tech stack.

Tech stack.

~/zpoken/work/panther/stack
Solidity · Base · Hardhat (Base + Basescan verification) · TypeScript dApp · Snapshot governance operations
— ENGAGEMENT

Talk to a founder.

Panther's Base deployment ran through the DAO's own governance, end to end — proposal, unanimous vote, verified contract, all in public.

The first step is a 30-minute call with a founder. Shapes, discovery, and terms → /engagement