Token

$ZECPASS is a Pons V2 token on Robinhood Chain. It is the thing a pass buys, and its fees are what pay for the road.

Terms

Term	Value
Name, ticker	Zecpass, ZECPASS
Launcher	Pons V2 (PonsV2LaunchAndBuy at 0xe33E9E479dF8802cb0866d5d05258bEc4cF62948)
Supply	1,000,000,000, all on the curve at launch
Pair	ETH
Curve	virtual reserve of 1.68 ETH; graduates to a Uniswap V4 pool with the Pons hook once 4.2 ETH have been paid in
Curve fee	1 percent on every trade, of which the creator share below
Creator tax	2 percent, paid to the treasury (0xe568F9e89F77D88399817Ec4046fa21Fc675E269)
Anti-snipe	99 percent tax for the first seconds after launch, then normal
Team allocation	none; the launch buy is the only creator position and it is public on the launch transaction

Where the money goes

Two streams reach the treasury.

1. Creator tax. Every trade of $ZECPASS on the curve, and later on the pool, credits 2 percent to PonsV2FeeEscrow. The treasury claims it with claim().
2. Hub fee. Every pass keeps 0.5 percent of the ETH before the buy and sends it to the treasury in the same transaction.

The treasury spends them in this order:

Use	How
Relayer gas on Robinhood Chain and Arbitrum One	plain transfers to 0x5C9A…951F
Fly.io machine and volume	off-chain, a few dollars a month
Hub vault, for instant mode	send ETH to the hub; it lands in the vault and turns into faster passes
Whatever is left	stays in the treasury; the whitepaper discusses buybacks as an option, nothing is promised

Nothing is automatic between the treasury and the vault by design: the vault's size is a decision about how much instant capacity to offer, and it is the only capital at risk in the system.

Launch procedure

The token is launched by hand on ponsfamily.com so that the launch transaction is visibly a person's, with the site, the docs and the hub already live.

1. Deploy the hub with token = 0 (the relayer and the site both say "not launched").
2. On Pons: name Zecpass, ticker ZECPASS, logo brand/logo-512.png, description from launch/description.txt, website the site URL, X the handle, creator fee recipient = treasury, creator tax 2 percent, launch buy of the founder's choice.
3. Read the token address on the Pons page or in the Launched event.
4. setToken(address) on the hub from the relayer or treasury key; set NEXT_PUBLIC_ZECPASS_TOKEN on Vercel and ZECPASS_TOKEN on Fly; redeploy the site.
5. Confirm on the stats page that the curve reads, then lockToken() from the treasury.

Between steps 3 and 4 the rails still work: ETH bridged to a pass simply waits, and the relayer sweeps it on the first tick after the token is set.

After graduation

At 4.2 ETH paid in, Pons sweeps the curve and anyone can create the Uniswap V4 pool. The hub's market adapter handles the gap itself (it creates the pool if it is the first to trade after the sweep). Passes keep working; the only visible change is the price source on the stats page.