How ZEEP works

ZEEP is a coin launcher on Robinhood Chain, built on Pons' V2 bonding curve. Launching a coin mints a regular Pons coin — nothing about that part is ZEEP-specific. What ZEEP adds on top is a reserve: at launch you pair the coin with one listed NFT collection and a fixed payout rule (raffle to holders, hold, or burn). From then on, a share of every trade is set aside for that collection's reserve.

A ZEEP coin itself is not a gacha or loot box. The only randomness in a coin is a raffle among its own existing holders, funded by trading fees the market already generated. The Gacha Station is a separate feature, explained below.

The launch wizard has four steps: name and image, the collection you're pairing with, the payout rule and creator tax, then a final review. Once you sign, the pairing is locked — the collection and outcome can't change after the coin ships, and no key, not even ZEEP's, can withdraw from the reserve; it can only buy the paired collection.

There is no dev buy in a ZEEP launch: your coin starts exactly at the curve's opening price, and you can buy your own coin from its page like anyone else.

Everything a coin costs and earns, with no small print.

Phase 2 contract design

• • 80% of everything a coin's creator side earns goes to its reserve, 20% to the ZEEP treasury.
• • The reserve can only buy at or under its posted price ceiling, which expires after 1 hour.
• • Purchases only ever happen through Seaport 1.6 — no other marketplace integration exists.
• • Withdrawals are disabled by design. Nothing, including ZEEP, can pull funds out except to buy the paired collection.
• • Harvesting accrued fees into the reserve is callable by anyone — it isn't gated behind a privileged account.
• • Raffle draws are seeded from a future block hash, so no one — including ZEEP — can see the outcome before it's committed.

The ZEEP treasury — the 20% side of that split — is a single wallet controlled by the ZEEP project owner, not a DAO or a governance contract. It receives the protocol's share the same mechanical way a reserve receives its own, and it has no access to any coin's reserve. See Contracts for the contract that enforces the split.

Pokémon and One Piece cards aren't native NFTs — they're tokenized by Courtyard.io, a real-world-asset vaulting platform: burn the NFT and Courtyard ships the physical, custodied card. Courtyard runs on Polygon and prices in USD/USDC, not ETH. A second card line, Collector Crypt, works the same way on Solana. Because neither lives on Robinhood Chain, pairing a coin with them goes through ZEEP's cross-chain contracts rather than the native ones.

The Gacha Station is powered by Collector Crypt on Solana. You pay a fixed USDC price for a sealed Pokémon or One Piece pack and receive one graded card, drawn at the odds published on each machine, as an NFT you can redeem for the physical card.

The machines, odds, prices and cards are Collector Crypt's — ZEEP shows them and lets you sign with your own Solana wallet. ZEEP coins and reserves aren't involved, and ZEEP never holds your funds.

Phase 1 — live. Coins launch as real, on-chain Pons coins, verified against the actual launch transaction before anything is recorded. Market data on every coin page comes straight from Pons.

Phase 1.5 — live, simulated. A scheduled keeper reads real on-chain Pons fee data for every coin, but purchases and raffle draws are logged, not executed — no private key, no real ETH moves. Every reserve panel running this way shows a "Simulated" badge. Until the router is deployed, Pons pays a coin's creator fees to the creator's own wallet.

Phase 2 — built and tested, not deployed. The on-chain contracts that actually buy, hold and raffle NFTs pass their test suite, but haven't been deployed, audited, or had a keeper wallet funded. See Contracts for what that system is made of.

Coins launched on ZEEP are experimental memecoins and can lose all value. Gacha pulls are random and a card can be worth less than its pack. Nothing on this site is financial advice.