privacy-pump-localnet

Maturity: Experimental developer tooling
Supported network: Local validator only
Audit status: Publication is not an audit. No external audit is claimed.

Ephemeral local development environment for Privacy Pump public examples.

Purpose

Offers disposable keys, local fixtures, mock interfaces, reset scripts, and smoke checks without production cloud or signer dependencies.

Scope

• Ephemeral key policy
• Mock relayer/access/metadata boundaries
• No persistent key directory

Architecture

flowchart LR
  User[Wallet or integrator] --> Interface[Public interface]
  Interface --> Boundary[Privacy Pump trust boundary]
  Boundary --> Chain[Solana or local reference]
  Boundary -. metadata exposure .-> Limits[Documented limitations]

Loading

See ARCHITECTURE.md for component boundaries and assumptions.

Current security status

• Experimental or reference material; not mainnet-ready.
• The inspected devnet programs are upgradeable and shared one upgrade authority at the publication audit date.
• Factory and relayer are distinct protocol roles, but a deployment may configure one signer for both.
• Production signer topology is intentionally not published.
• The ZK Pool vault-creation fee receipt does not independently bind its signer named factory to the Private Vault config factory; that boundary is under review.
• The ZK verifier path is fail-closed by default and is not a complete production privacy system.
• Browser, RPC, relayer, database, Waku/Logos, and Arcium metadata each have separate privacy limitations.
• Custom cryptographic glue is not described as audited.

Read SECURITY.md before using any material.

Dependencies

• privacy-pump-private-vault-program
• privacy-pump-sdk

Local setup

Use deterministic fixtures and ephemeral local keys only. No production credentials, cloud accounts, private RPC endpoints, or real wallet relationships are required.

node scripts/policy-scan.mjs

npm install
npm test
node scripts/create-ephemeral-keypair.mjs

The key-generation script writes only to a fresh operating-system temporary directory and prints the public key. It must never be adapted to a persistent tracked key directory.

Roadmap

• Pin public releases
• Add deterministic smoke flow
• Add container option after review

Related Privacy Pump repositories

• privacy-pump-private-vault-program
• privacy-pump-sdk

Known limitations

• Public content omits production relayer, access-control, KMS, Supabase service-role, keeper-signing, monitoring, and deployment implementations.
• Privacy depends on more than user-interface masking; metadata visible to wallets, RPCs, relayers, transports, and infrastructure remains relevant.
• Interfaces may change while the devnet architecture is stabilized.

Contributing

See CONTRIBUTING.md. Licensing is under review; see LICENSE_STATUS.md.