Security model

Zonk.fun is non-custodial at the wallet layer: users sign from a selected external EVM wallet or a user-controlled Privy embedded wallet, and the application and backend never receive wallet keys. Transactions require the user to approve signing; there is no delegated or backend signing path. The protocol contracts, however, hold curve principal, fee liabilities, vault allocations, and permanent LP assets according to their code.

Trust boundaries

Boundary	Assumption and risk
Browser and wallet	User verifies origin, network, target, value, approval, and slippage
Smart contracts	Bugs or unexpected interactions can cause loss despite tests and invariants
Tokens and markets	Permissionless tokens may be misleading, volatile, illiquid, or worthless
Uniswap V3	External protocol, pools, periphery, and market behavior add dependency risk
RPC providers	Can be delayed, unavailable, rate-limited, or return inconsistent reads
API/indexer	Can lag or display incomplete data; not authoritative for balances or settlement
Metadata links	Creator-provided content may be inaccurate or malicious

The repository contains extensive unit, invariant, integration, and fork-test code. That is engineering evidence, not a claim of a completed independent external audit. No “risk-free” or “fully secure” claim is made.

Smart-contract transactions are irreversible. Use only amounts you can afford to lose and verify every wallet prompt.

Overview

Getting Started

Using Zonk.fun

Protocol

Contracts

Developers

API Reference

Operations

Security

Reference

Trust boundaries

​Trust boundaries

Trust boundaries