Understand what you’re using.

$ZP, the Zippad platform token.

The supply, curve, fees, and graduation rules below describe tokens created on Zippad. $ZP follows its own launch settings on Stockereum.

Every launch starts on equal terms.

Zippad creates a fixed-supply ERC-20, a bonding curve, and a dedicated Privacy Pool in one transaction. The creator receives no reserved tokens. There is no extra minting function or transfer tax.

Total supply

1,000,000,000 tokens

Available on the curve

800,000,000 tokens

Reserved for liquidity

200,000,000 tokens

Launch fee

0.005 ETH plus network gas

The price follows a constant-product curve with virtual reserves. Buys raise the price; sells lower it. Quotes use the contract’s current state, and your minimum received amount protects against price movement up to your selected slippage.

A curve with a destination.

When all 800 million curve tokens have been sold, the final purchase automatically creates liquidity from about 3 ETH of net proceeds and the 200 million reserved tokens. The Uniswap v2 LP shares go to an immutable lock with no withdrawal function.

If the last purchase exceeds the curve’s remaining capacity, unused ETH becomes a credit the buyer can claim. Creator fees and treasury fees are also claimable credits; they are separate from trading reserves.

Curve trades charge 1%: 0.5% to the creator and 0.5% to the treasury. After graduation, trades use Uniswap v2 and its 0.3% pool fee. Zippad does not charge a continuing tax on those trades. Small rounding differences are possible at the transition.

Private linkage, public settlement.

ZipCoin uses 0xbow’s Privacy Pools. Zippad reuses that commitment and proof model. To “zip,” you deposit tokens directly from your wallet. The contract records a commitment to a secret note. After the deposit enters an association set, a proof can withdraw some or all of that note to another address.

The proof establishes membership in both the token’s pool and its approved association set without naming the original deposit. It also binds the destination and relay fee. A relayer pays the gas, allowing the recipient to receive tokens without first funding that address from the depositing wallet.

Each token has a separate pool and entrypoint. Activity in another token’s pool does not increase this token’s anonymity set. “Eligible deposits” counts approved deposit notes, not unique people.

Your privacy key is a spending secret.

Zippad generates a separate random recovery phrase in your browser. Back it up before depositing. It stays in memory and is cleared when the page reloads; importing your saved privacy phrase recovers notes from public events. Never enter your ordinary wallet seed phrase here.

If the association service or relayer becomes unavailable, you can use “Exit publicly.” This requires your note secrets, the original depositing wallet, and enough ETH for gas. An approved private withdrawal can use the phrase through a relayer; public exit cannot bypass the original-wallet requirement.

A public exit reveals the note’s deposit label. Exiting a change note after a partial private withdrawal can link that earlier withdrawal to the depositor. Losing both the privacy phrase and any compatible recovery path can make funds inaccessible.

Know the boundaries.

• Application contracts are unaudited. Upstream Privacy Pools audits do not cover Zippad’s factory, token, curve, operator, or interface. An independent audit is required before a public launch involving real funds.
• Pool administration is sealed. Each entrypoint’s owner is the registrar, which exposes no upgrade or owner-management function. The deployment pins the pool implementation and verifiers.
• The association provider can deny approvals. The deployed postman address is fixed. It can publish roots, but cannot spend a note without its secrets. A failed or lost postman key may require public exits.
• Local admission is development-only. The local operator approves after a delay. This is not compliance screening. Production uses an explicitly configured allowlist policy and per-token enablement.
• The relayer may stop. It uses a capped ETH budget. Token fees may not cover its costs; availability depends on funding, policy, and network conditions.
• Only factory-created standard tokens are supported. Transfer-tax and rebasing tokens can break nominal pool accounting.
• Your browser and RPC matter. A compromised frontend or extension could expose secrets or mislead you. Verify addresses and transaction details in your wallet.

Read the code behind the idea.

ZipCoin provided the starting point for this project. Zippad is independent and is not affiliated with ZipCoin, 0xbow, or Vitalik Buterin.

The repository’s research report records source comparisons, artifact hashes, unresolved deployment claims, and the changes made for this launchpad.