A story worth speaking into.

A coin. A message. A doorstep.

In Vitalik Buterin’s Snowmoon, cryptography sits quietly behind ordinary lives. People work, meet friends, make choices, and sometimes spend zipcoins to ask for someone’s attention. A costly message can open a conversation; it cannot demand a reply.

Zipcoin brings the burn and doorstep idea to Ethereum. zipped extends it to communities: a coin’s trading activity can fund messages at a chosen doorstep. The launchpad and its fee-funded vault are our own adaptation.

Launch. Trade. Burn. Speak.

The burn launch system is awaiting activation. Existing tokens keep their original trading and privacy rules; the new mechanics below apply to the new launch version.

New-version coins pair with unzipped $ZC on Ethereum. Every buy and sell through their official zipped pool contributes 1% in $ZC. That includes the creator’s first purchase. Other trading venues may have different fee rules.

Creators can enter an ENS name or Ethereum address. We show the resolved address before launch and keep it as the coin’s destination. Changing an ENS record later does not redirect existing launches. Leave the field blank for a general announcement.

Every ten minutes, the operator checks each coin’s burn balance. A burn needs at least 1,000 $ZC and sufficient shared gas reserves. It calls Zipcoin’s official Doorstep contract, which sends the coins to the dead address and records the message. The message is eligible for Zipcoin’s public feed; its appearance depends on their indexer.

1250.5 $ZC HAS NOW BEEN BURNT BY $MOON

This is an example. Actual messages contain the exact amount burned and the launching coin’s ticker. Sending coins to a burn address without calling the Doorstep contract does not publish a message.

One vault. Separate voices.

80% of collected fees

The originating coin’s protected burn balance

20% of collected fees

Platform gas and revenue

Gas asset

ETH, acquired by converting platform $ZC

Low balance

Wait and accumulate; no automatic external top-up

The split is of the collected 1% fee. For example, 10,000 $ZC in fees allocates 8,000 $ZC to the coin’s burns and 2,000 $ZC to platform operations. Gas conversions never touch the 8,000 $ZC. A shared ETH reserve supports all new-version coins, and revenue is withdrawable only above its protected reserve.

The platform initially funds ETH to start the worker. After that, automated gas funding uses vault funds and conversions of the platform’s 20% allocation. Low revenue, expensive gas or an unavailable conversion route can delay burns. An eligibility countdown is not a promise of a mined transaction.

Admin controls include pausing automation, managing the keeper and withdrawing permitted platform surplus. Burn allocations cannot be withdrawn as revenue. The platform separately controls its liquidity positions and can remove its liquidity.

New launches create one billion tokens and a dedicated Uniswap v4 token/$ZC pool. The creator’s ETH contribution buys $ZC through the verified Stockereum route. Half of the received $ZC seeds liquidity alongside the token supply; the remainder buys tokens for the creator. Both conversions have minimum received amounts and a deadline. The official pool collects the 1% contribution through its hook, including trades made with other compatible routers. Wallet transaction gas is paid by the creator or trader.

Privacy beneath the story.

zipped keeps the Privacy Pools technology used by ZipCoin available to holders. Every launch has a dedicated privacy pool. Trading and automated treasury messages remain public; zip / unzip is a separate choice.

Shared privacy core

0xbow Privacy Pools, as used by ZipCoin

Same circuit artifacts

Groth16 proving keys, verification keys, and browser WASM

Same note model

Secret commitments, nullifiers, and partial-withdrawal change

Added by zipped

Token creation, $ZC liquidity, and fee-funded Doorstep messages

What “the same technology” means.

Our six commitment and withdrawal circuit files match the reviewed ZipCoin artifacts byte for byte. zipped uses the same pool and proof construction, with its own deployed verifier instances. A valid withdrawal proves note ownership and membership in the approved deposit set without identifying the deposit it spends.

zipped’s launch contracts, pool isolation, and operator are separate integrations. Each token has its own pool and entrypoint. Recovery starts from a random privacy phrase instead of ZipCoin’s wallet-signature flow. Original launch versions 1–3 do not include burn-to-speak or Doorstep. The new launch version adds the shared vault and public Doorstep calls described above.

zipped is independent. Shared open-source technology does not imply affiliation with or endorsement by ZipCoin or 0xbow, and does not extend upstream audits to zipped’s application contracts.

$ZP, the zipped platform token.

The supply, liquidity, and fee rules below describe tokens created on zipped. $ZP follows its own launch settings on Stockereum.

Original launch versions.

This section records the existing ETH-paired launch rules. New $ZC-paired launches use the version-specific rules and quotes in their launch form.

zipped creates a fixed-supply ERC-20, funded Uniswap v2 liquidity, 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

Initial liquidity allocation

Full supply paired with the creator’s ETH contribution

Creator tokens

Required purchase equal to the ETH liquidity contribution

Launch fee

Read from the active contract and shown separately on the launch form. Creator funding and network gas are additional.

The creator provides ETH liquidity, subject to the minimum shown on the launch form. New managed launches require at least 0.02 ETH in creator funding: 0.01 ETH seeds liquidity and 0.01 ETH buys tokens. The active contract’s launch fee is shown separately, plus network gas. An equal, required creator purchase executes against the funded pair in the same transaction, with a minimum received amount and a deadline. Failure reverts the whole launch.

Original ETH-paired liquidity & fees.

The following rules apply to original launch versions 1–3. The $ZC pool and 80/20 fee allocation described above apply to new launches.

The full billion-token supply and the creator’s ETH contribution seed the canonical Uniswap v2 token/WETH pair. For new managed launches, the platform treasury wallet receives the initial LP shares directly. That wallet may transfer its shares or remove its proportional liquidity; it can add liquidity using tokens and ETH it owns. The shares are not permanently locked. Required creator purchases and subsequent trades move tokens out of that pool at its current price.

Trades use Uniswap v2 and its 0.3% pool fee. There is no additional creator or platform swap fee and no token transfer tax. The launch fee is separate from liquidity and purchase funds. Withdrawing the platform’s liquidity can leave dust reserves, so usable liquidity is not guaranteed after withdrawal. Owning LP shares gives no authority over other providers’ shares or administration of the Uniswap pair.

A funded pool can trade immediately after the launch transaction confirms. External services such as DexScreener may take time to discover and display it. zipped charts show indexed on-chain swaps; an empty history does not mean the pool is unfunded.

Tokens created by an earlier zipped factory retain their original trading contracts, fees, and privacy pools. Earlier version 2 launches retain permanently locked initial LP shares; version 1 tokens retain legacy curve trading or their original locked graduation liquidity. Their token pages disclose the applicable custody. Existing holders can still buy, sell, zip, unzip, and exit publicly.

Zip, prove, unzip.

ZipCoin uses 0xbow’s Privacy Pools. zipped uses the same commitment model and Groth16 circuit artifacts. 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.

zipped 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 zipped’s factory, token, liquidity integration, 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.
• Admission requires a waiting period. The mainnet operator accepts deposits into factory-created token pools after 12 blocks and a five-minute delay. Root publication may add further waiting time. This policy does not screen depositors.
• 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’s open-source privacy implementation is the foundation. zipped 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.