# Launch ZKP on BASE **URL:** \ **Category:** Panther Ecosystem\ **Created:** [August 8, 2023, 10:50am UTC](https://forum.pantherprotocol.io/t/launch-zkp-on-base/330 "2023-08-08T10:50:56Z")\ **Posts on this page:** 6\ **Page:** 1
**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:** [August 8, 2023, 10:50am UTC](https://forum.pantherprotocol.io/t/launch-zkp-on-base/330/1 "2023-08-08T10:50:56Z")
Hey guys! Opening this topic to discuss the possibility of launching of ZKP on the BASE L2 network…please provide your inputs on the same! Thanks ---
**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:** [August 8, 2023, 10:52am UTC](https://forum.pantherprotocol.io/t/launch-zkp-on-base/330/2 "2023-08-08T10:52:44Z")
This is a new and trending ecosystem launching on the 9th of August (tomorrow)! And would help enhance the visibility of V1 come launch! ---
**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:** [October 23, 2025, 1:57pm UTC](https://forum.pantherprotocol.io/t/launch-zkp-on-base/330/3 "2025-10-23T13:57:41Z")
I think now we are nearing the POLYGON Launch it may be interesting to see if anyone out there would be willing and capable of launching the protocol on Base for us? ---
**Author:** ![reuben](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/reuben/32/231_2.png) [@reuben](https://forum.pantherprotocol.io/u/reuben)\ **Post date:** [October 26, 2025, 3:49pm UTC](https://forum.pantherprotocol.io/t/launch-zkp-on-base/330/4 "2025-10-26T15:49:15Z")
So Base might be a good second chain to launch on. The existing code is easier to integrate with other L2s vs let’s say a completely new chain like Solana or even those that aren’t Eth L2s like BNB Chain. It has a strong ecosystem and recently it looks like they’re looking at privacy preserving stablecoins. Panther with its architecture I think is a good fit. ---
**Author:** ![Towel](https://avatars.discourse-cdn.com/v4/letter/t/b2d939/32.png) [@Towel](https://forum.pantherprotocol.io/u/Towel)\ **Post date:** [October 27, 2025, 11:37am UTC](https://forum.pantherprotocol.io/t/launch-zkp-on-base/330/5 "2025-10-27T11:37:41Z")
I agree if we can get ourselves promoted on a existing L2 with new traffic without having to do to much work to integrate. That’s the way to go. ---
**Author:** ![zpoken](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pantherprotocol.io/zpoken/32/298_2.png) [@zpoken](https://forum.pantherprotocol.io/u/zpoken)\ **Post date:** [October 27, 2025, 12:05pm UTC](https://forum.pantherprotocol.io/t/launch-zkp-on-base/330/6 "2025-10-27T12:05:04Z")
Zpoken Proposal – Panther Protocol Base Network Enablement **Applicant:** Zpoken OÜ (independent open‑source contributor) **Category:** Research & Tooling (non‑operational) **Networks Covered:** Base & Base Sepolia (configuration/testing only; **no live deployments** ) **License:** MIT (or Apache‑2.0, at Foundation’s preference) * * * ## 1) Summary This grant funds **open‑source research, configuration, scripts, and documentation** that enable **independent third parties** (e.g., a DAO, community operators) to later deploy Panther Protocol on **Base**. The work is **non‑custodial** and **non‑operational** : **no on‑chain deployments, no UI operation, no multisig/treasury control, and no user‑funds interaction**. Outputs are public, reproducible, and licensed permissively. * * * ## 2) Motivation & Problem The Panther codebase is EVM‑compatible but lacks a **policy‑compliant, reproducible path** tailored for Base. Ecosystem operators need clear **network configs, deployment/verification scripts, parameter templates, and a runbook** to execute independent deployments without relying on service providers or violating Foundation policy (no direct operations). This grant produces exactly those artifacts. * * * ## 3) Scope of Work (In‑Scope) 1. **Hardhat Network Enablement** 2. **Simulation & Compatibility Testing** 3. **Deployment Runbook (for independent operators)** 4. **Open‑Source Publication** * * * ## 4) Explicit Exclusions (Out‑of‑Scope) - **No deployments** to Base mainnet by the grantee. - **No UI operation/hosting** or user‑facing service. - **No custody of keys** , no multisig/treasury management, no relaying, no upgrades. - **No user‑funds interaction** and no production monitoring/on‑call. - **No brand/UI operation** beyond documentation and disabled code samples. * * * ## 5) Deliverables 1. **Network Configuration Pack** 2. **Automation Scripts** 3. **Deployment Runbook** (Markdown/PDF) 4. **Parameter Registry Templates** 5. **Final Technical Report** 6. **(Optional) Extras** * * * ## 6) Milestones & Budget **Total Grant Requested:** **USD 14,000 equivalent** | Milestone | Scope | Artifacts | Acceptance | Payout | | --- | --- | --- | --- | --- | | **M1 – Base Enablement Pack** | Hardhat configs, deterministic builds, scripts skeleton; parameter templates v1 | PR with configs; `.env.example`; build artefacts; docs draft | Maintainer review + basic CI green | **$7,000** | | **M2 – Runbook & Final Report** | Full runbook (deploy/verify/rollback), verify helpers, local smoke‑tests, final technical report; optional subgraph/UI stubs (disabled) | Published repo & docs; CI passing; tagged release v1.0 | Maintainer approval + publication under permissive license | **$7,000** | > Note: No on‑chain actions by grantee are required for acceptance. * * * ## 7) Reporting & Communication - Weekly progress notes (short written update). - Code reviews via PR in a public repo. - One closing call/written summary upon grant completion. * * * ## 8) Dependencies & Inputs (Non‑Operational) - Public RPC endpoints and Basescan API keys **for documentation/examples only**. - Community‑provided example addresses for **templates** (multisigs, treasuries, trustProvider), **not used by the grantee**. - Token metadata for sample zAsset templates (e.g., WETH, USDC) to illustrate configuration. * * * ## 9) Team & Track Record - **Zpoken OÜ** – independent R&D team with deep EVM experience (smart contracts, tooling, L2s) and prior contributions across Interoperability/DeFi/RWA. - Key skills: Hardhat/Foundry, Solidity build chains, verification tooling, CI, reproducible deployments, ZK and cryptography. * * * ## 10) Compliance Statements - **Independent Status:** The grantee acts independently and **does not** operate or deploy Panther Protocol on any network. - **No Operations/No Custody:** No UI operation/hosting; no keys; no funds; no multisig/treasury management; no upgrades/relaying. - **Open‑Source Licence:** All outputs released under **MIT (or Apache‑2.0)** with the following disclaimer placed prominently in each repo: - **No Incentives Tied to TVL/usage:** Payment strictly milestone‑based; **no performance fees** , no rev‑share, no token‑based compensation. - **No User Data:** The work does not process or retain user data. * * * ## 11) Timeline 3 calendar weeks from kickoff for M1→M2 handover (non‑operational). This is informational only and does not imply any on‑chain activity.