zerotracedocs

ZERO on Pons

What ZERO is, the Pons V2 terms it trades under, who receives its fees and how to check them on-chain, and how the ZeroTrace contracts are deployed around it.

ZERO is created by the Pons V2 launchpad on Robinhood Chain (chain 4663). ZeroTrace adds nothing to the token: it is a plain ERC-20, and ZeroTrace is a set of contracts deployed around it.

The token

ItemValue
ZERO (0x316fa3AB9A8FD8d7567a823DedecF28d9FEE2894)PonsV2LauncherToken: OpenZeppelin ERC20 + ERC20Burnable, 18 decimals, no owner, no transfer restrictions; the whole supply is minted once, in its constructor
Name, symbolzerotrace, ZERO. The name is also the vault's EIP-712 domain name
Supply1,000,000,000 ZERO, all minted to the bonding curve
Team allocationNone: no treasury, no reserve. Every ZERO starts in the curve; the team can hold ZERO only by buying it like anyone else

Its Pons terms

Pons fixes these terms when it creates a token, and they cannot change afterwards.

TermValue
Quote assetNative ETH (pairToken = address(0))
Standard fee1% of every trade (curve.feeBps()), the same on the curve and after graduation, in ETH
Pons' share30% of the standard fee (protocolFeeShareBps 3000): 0.3% of a trade
Creator tax0 (creatorTaxBps)
BuybacksOff (buybackEnabled false): the whole creator share is paid in ETH
Curve (0xE276F7E250bC2cD45f1e344d9adc9c9687c2c897)Trades ZERO for ETH until graduation. See The market
GraduationWhen the curve has collected 4.2 ETH (graduationThreshold), into a Uniswap v4 pool: native ETH / ZERO, fee 0, tick spacing 200, the Pons meme hook
Opening snipe taxPons' rule for every launch: 99% of a buy, decaying to 0 over the first 5 seconds; addresses named at launch are exempt, as Pons allows

Who receives the fees

ZERO's creator fee recipient on Pons is the fee harvester. The creator share of every trade fee, 0.7% of the trade, goes to it in ETH, and its permissionless harvest splits it in half:

HalfShare of each tradeUse
The team's0.35%Paid to the team's recipient
The holders'0.35%Keeps the vault's EntryPoint deposit at 0.1 ETH, then buys ZERO donated to the vault

The network fees of private operations go to holders, not to the team. See The vault and Gas.

ZERO launched with a fee harvester as its creator fee recipient, and each harvester hands the role on to the next; the earlier ones are listed in Deployments. The vault's harvester is a FeeHarvesterV3 (0xe2f2341AE7C0f8f520216001bc8B9087465Cf856). DeployV3.s.sol proposes it as the successor of the harvester that receives the fees when the vault is deployed, a FeeHarvesterV2, whose successor procedure waits 24 hours: from then on anyone can execute the proposal, which calls Pons' transferCreatorFeeRecipient, and the fees go to FeeHarvesterV3. Fees credited to the previous harvester before then stay claimable by it. Each harvester donates to the vault set in its constructor, so the hand-over also brings the holder yield to the vault.

FeeHarvesterV3 has no delay of its own: its owner hands the role on at once with handOver(successor). See Owner and successor.

The wallet that made the launch has no special rights over ZERO: it cannot sweep ZERO's fees or redirect them. The creator fee recipient changes only through the harvester in charge, or by Pons' owner after a 3-day timelock; see Trust model.

Check it on Pons

Everything above is in Pons' own record of the token, which anyone can read from the factory (0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e):

PonsLaunchedToken memory t = ponsFactory.getLaunchedToken(zero);
// t.exists              true
// t.creatorFeeRecipient the harvester in charge: each one hands the role on to its successor
// t.pairToken           address(0): native ETH
// t.creatorTaxBps       0
// t.buybackEnabled      false
// t.curve               ZERO's bonding curve

The curve reports the same terms (feeBps, creatorTaxBps), and IERC20(zero).totalSupply() is 1,000,000,000 × 10^18. pendingCreatorFeeRecipient on the factory shows any redirect Pons' owner has started.

The harvester and ZERO's Pons record

Every harvester takes ZERO's address in its constructor and reads Pons' record of it. Deployment reverts unless Pons launched the token (NotAPonsLaunch) and pairs it with ETH (NotAnEthPair). Before deploying the launch harvester, the deploy script's check also required that Pons names its planned address as ZERO's creator fee recipient. A later harvester becomes the recipient only when its predecessor hands the role on. See FeeHarvester.

The ZeroTrace deployment

The contracts deployed with ZERO's launch went through CreateX's CREATE3 (0xba5Ed099633D3B313e4D5F7bdc1305d3c28ba5Ed), with a salt only the deployer can use and that includes the chain ID. Each address depends only on the deployer, the chain and a salt label, so it was fixed before anything was deployed, and nobody else can deploy at it. The Poseidon2 hasher deployed then (0xb63c2AA1370B32CcfABaf5d24F854D817b405833) is the one the vault uses. See Deployments.

The vault is deployed by two scripts, with a plain CREATE, from the addresses in deployments/4663.json.

DeployVerifier.s.sol

Requires the verifier source to open the grand sum at 1 (NUM_SMALL_IPA_OPENING_CLAIMS = 5).

Deploys HonkVerifier, after forge deploys and links its two libraries, RelationsLib and ZKTranscriptLib, and records it as verifierV3.

It is a script of its own because it must not import the vault: the vault is compiled at 200 optimizer runs to fit the contract size limit, and so is everything compiled with it, while the verifier is the 10,000-run build.

DeployV3.s.sol

It must be run by the owner of the harvester that Pons names as ZERO's creator fee recipient, with no successor already proposed. Before broadcasting anything it checks that the verifier source opens the grand sum at 1, that the hasher computes the same hash_2 and hash_3 as the Yul Poseidon2 library, and that the deployed verifier has the code size of this repository's 10,000-run build and accepts the repository's fixture proof. Then, in one run, it:

Deploys the PrivateVault implementation with ZERO, the Pons factory, the curve, the PoolManager, the graduated pool ID, the verifier, the hasher and the EntryPoint, and the EIP-712 name TOKEN_NAME (default zerotrace).

Deploys the ERC1967Proxy over it, which calls initialize(OP_COST_WEI, ADMIN, UPGRADER, GUARDIAN). OP_COST_WEI defaults to 0.0002 ETH and GUARDIAN to the deployer. On Robinhood Chain ADMIN and UPGRADER must be set explicitly; elsewhere they default to the deployer.

Deploys a PrivateRouter for the vault.

Deploys a FeeHarvesterV3 for the vault, with the current harvester's target deposit and team recipient, owned by HARVESTER_OWNER (default the current harvester's owner).

Buys the vault's locked seed through the new router with SEED_ETH (default 0.001 ETH), with stub = keccak256("zerotrace/locked-seed") mod p and an empty ciphertext. Nobody can spend it; see The vault. The buy pokes the vault, which sets its price average and first network fee.

Deposits GAS_DEPOSIT (default 0.1 ETH) in the EntryPoint for the vault.

Calls proposeSuccessor on the current harvester with the new one. After its 24-hour delay anyone can run the script's execute(), which calls executeSuccessor(), and Pons then pays ZERO's creator fees to FeeHarvesterV3.

After the run it checks that the vault uses the new verifier, that each role is held where it was meant to go, that the deployer holds neither the admin nor the upgrader role unless it was named for it, and that the vault is not paused. It writes the addresses to the deployment file as vaultV3 (the proxy), vaultV3Implementation, routerV3 and harvesterV4, and the seed's ZERO as seedTokensV3.

At launch the deployer, 0x1B0210b9695BbEB8bD70964A46bf512021127A73, holds the vault's three roles and owns the harvester. See Roles.

What buyers see

At the startValue
Where ZERO tradesThe Pons bonding curve, until graduation
Fees on a trade1% standard fee, in ETH: 0.3% to Pons, 0.7% to the harvester (0.35% to the team, 0.35% for holders)
First 5 secondsThe Pons snipe tax on buys
ZERO held by ZeroTraceThe locked seed only
Where a purchase landsA private note through PrivateRouter.buy; public ZERO through any other route, shielded with one call. See Public ZERO and shielding

Early on few notes exist, so the set of notes a spend could come from is small; see Staying private.

On this page