zerotracedocs

Deployments

Network details, the addresses of the vault, its router and harvester, the Pons contracts ZERO trades on, and the public bundler of ZeroTrace on Robinhood Chain.

Network

FieldValue
NetworkRobinhood Chain
Chain ID4663
RPC URLhttps://rpc.mainnet.chain.robinhood.com
Explorerrobinhoodchain.blockscout.com
Native currencyETH, 18 decimals
Appzerotrace.so

On Robinhood Chain, block.number follows the Ethereum L1 block, about 12 seconds. The vault's price average counts these blocks (see Gas).

ZeroTrace runs only on Robinhood Chain mainnet, because Pons V2, the launchpad ZERO is created on, exists only there.

Contract addresses

ContractAddressWhat it is
ZERO0x316fa3AB9A8FD8d7567a823DedecF28d9FEE2894The token: a plain ERC-20 created by Pons V2, no owner, no transfer restrictions
Pons bonding curve0xE276F7E250bC2cD45f1e344d9adc9c9687c2c897Where ZERO trades against ETH until it graduates. Pons' contract, one per token
PrivateVault (proxy)0xEE92d20c1b0AAA686DDc8809A1B6A67aB092eb33The vault, and the address everyone uses: an ERC-1967 proxy holding shielded ZERO, the key registry, the note tree, nullifiers, vault shares, the price average, and the ERC-4337 account of private actions
PrivateVault (implementation)0xBc08FAd89f924e1A852D271061977d0fCE40A559The code behind the proxy at deployment. The upgrader can point the proxy at another implementation; read the current one from the proxy's ERC-1967 implementation slot
PrivateRouter0x0c242A7E0717D09A5517AD1de282CCb66533365dBuys ZERO into a note, sells a note for ETH, quotes
FeeHarvesterV30xe2f2341AE7C0f8f520216001bc8B9087465Cf856The vault's harvester. Once the hand-over to it executes, ZERO's Pons creator fee recipient: it sends half of the creator fees to the team and turns the other half into gas and ZERO for the vault
HonkVerifier0x8F27B4B83bd86F11A07E3FFe0369Cb4B08a60735UltraHonk verifier of the transact circuit, an immutable of the vault's implementation
Poseidon2 hasher0xb63c2AA1370B32CcfABaf5d24F854D817b405833Poseidon2 over BN254, used by the note tree
NoteRefund (proxy)0x702DF8c7b312b06Fc6947Faf788C5deF7776DBE1Refunds the earlier vault's notes, each once, into notes of the vault; its own ERC-4337 account pays the gas. See Refund of the earlier vault

ZERO's and the curve's addresses are chosen by Pons when it creates ZERO. Pons' record of the token names the creator fee recipient: factory.getLaunchedToken(zero).creatorFeeRecipient.

The vault's operation cost, what the network fee is worth in ETH, is 0.0002 ETH at deployment; the guardian can set it between 0.00005 and 0.001 ETH. Its roles are held by the deployer at launch:

RoleHolder at launchWhat it can do
DEFAULT_ADMIN_ROLE0x1B0210b9695BbEB8bD70964A46bf512021127A73Grant and revoke every role
UPGRADER_ROLE0x1B0210b9695BbEB8bD70964A46bf512021127A73Replace the vault's implementation, with no delay
GUARDIAN_ROLE0x1B0210b9695BbEB8bD70964A46bf512021127A73Pause every spend, pause entries, pause exits to a target, set the operation cost
Harvester owner0x1B0210b9695BbEB8bD70964A46bf512021127A73Change the team's recipient, hand ZERO's creator fee recipient to another contract at once

Read the live holders on-chain with hasRole(role, account) and the RoleGranted and RoleRevoked events on the vault, and owner() on the harvester. See Trust model.

Earlier contracts

ContractAddressWhat it is
PrivateVault, earlier vault0xf3935bec6247170B28e1755c85957A72f243D84DClosed: entries paused, no shares outstanding. The key-derivation and payment-link messages still name its address, so wallets keep their keys and private address
FeeHarvesterV20x276B8ba2e38a5e1CB43FF3493e620CFF6cEC4878Earlier harvester. Receives ZERO's creator fees until the hand-over to FeeHarvesterV3 executes, 24 hours after the vault's deployment
FeeHarvester0x8416DA7325cc619A5E560D8Ef6f413e94950CAd5The launch harvester. Keeps spending the fees already credited to it

Deployment

Two scripts deploy the vault, each with a plain CREATE:

script/DeployVerifier.s.sol deploys HonkVerifier, built at 10,000 optimizer runs, with its two linked libraries RelationsLib and ZKTranscriptLib, and records it as verifierV3.

script/DeployV3.s.sol, run by the owner of the harvester ZERO's fees go to, checks the verifier source, the hasher and the deployed verifier (its size, and that it accepts the repository's proof). It then deploys the vault's implementation and its ERC1967Proxy, initialized with the operation cost (OP_COST_WEI, 0.0002 ETH by default) and the roles (ADMIN, UPGRADER, GUARDIAN; on Robinhood Chain ADMIN and UPGRADER must be named explicitly). It deploys the router and the FeeHarvesterV3 (owner HARVESTER_OWNER), buys the locked seed note through the router (SEED_ETH, 0.001 ETH by default), deposits gas for the vault in the EntryPoint (GAS_DEPOSIT, 0.1 ETH by default), and proposes the new harvester as the current one's successor.

DeployV3.s.sol's execute(), which anyone may run 24 hours later, executes the hand-over.

The harvester handover

ZERO's creator fee recipient is a harvester, and Pons pays ZERO's creator fees to whichever harvester its record names. FeeHarvesterV2 holds the role when the vault is deployed. DeployV3.s.sol deploys FeeHarvesterV3 with V2's team recipient and target deposit and, in the same run, calls proposeSuccessor on V2 with it. Anyone can call executeSuccessor() on V2 once its successorReadyAt() has passed, 24 hours after the proposal. From then on Pons pays ZERO's creator fees to FeeHarvesterV3, which buys ZERO for the vault. Fees already credited to V2 stay there.

FeeHarvesterV3 hands the role on differently: its owner calls handOver(successor) and the change takes effect at once, with no proposal and no delay.

FieldValue
FeeHarvesterV3 owner0x1B0210b9695BbEB8bD70964A46bf512021127A73 (the deployer): may change the team's recipient and hand the fee recipient over
FeeHarvesterV3 team recipientV2's, 0x1B0210b9695BbEB8bD70964A46bf512021127A73
FeeHarvesterV3 target depositV2's, 0.1 ether

Check it on-chain: pendingSuccessor() and successorReadyAt() on V2 before the handover, creatorFeeRecipient in Pons' record after it.

Pons V2

ContractAddress
PonsV2LaunchFactory0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e
PonsV2MemeHook (the factory's memeHook())0xE5e702641Ea86F4ae6cC3cDaeD2B886f976Be044
Pons fee escrow0xd3AFEB2a57f70eF218Aa82451c51B2fb0416Ac9e

The router and the harvesters read the hook from factory.memeHook() at deployment, and it is the address above.

Shared infrastructure

Deterministic addresses

The contracts of ZeroTrace's first deployment, the hasher and the launch harvester among them, were deployed through CreateX's CREATE3, with a salt that only the deployer can use and that includes the chain ID. An address therefore depends only on the deployer, the chain and a salt label (zerotrace-v1), not on the contract's bytecode. The mainnet deployer is 0x1B0210b9695BbEB8bD70964A46bf512021127A73, so those addresses were fixed before deployment, and ZERO launched with the launch harvester's planned address as its creator fee recipient. ZERO's and the curve's addresses are not: they are set by Pons. FeeHarvesterV2 was deployed later with a plain CREATE (script/DeployHarvesterV2.s.sol), and so are the vault's verifier, implementation, proxy, router and harvester (script/DeployVerifier.s.sol, script/DeployV3.s.sol).

Where ZERO trades

ZERO trades in two places over its life, both run by Pons. It graduated within seconds of its launch on 2 October 2026, so today it trades only on the pool:

  1. The bonding curve, from launch until it has collected 4.2 ETH.
  2. The graduated Uniswap v4 pool, after that. Graduation takes two permissionless calls on the factory, graduate (sweeps the curve) and createGraduatedPool (seeds the pool). The router and the harvesters make them themselves on the next trade if nobody else has.

The graduated pool's PoolKey:

FieldValue
currency00x0000000000000000000000000000000000000000 (native ETH)
currency1ZERO, 0x316fa3AB9A8FD8d7567a823DedecF28d9FEE2894
feethe launch's poolFee (0)
tickSpacingthe launch's tickSpacing (200)
hooksPonsV2MemeHook, 0xE5e702641Ea86F4ae6cC3cDaeD2B886f976Be044

Only the Pons factory can initialize a pool with its hook, so nobody can open this pool first. A pool with any other key (another fee, tick spacing or hook) has another pool id and is ignored by the router, the harvesters and the price average. Fees are the same before and after graduation. See The pool.

Aggregators already route Pons tokens on Robinhood Chain, on the curve and on graduated pools. See Integrations.

Bundler

Private actions (send, sell, unshield, payment-link claims) reach the chain as ERC-4337 UserOperations whose sender is the vault. The app uses Pimlico, which lists Robinhood Chain (4663) with EntryPoint v0.8:

FieldValue
Endpointhttps://api.pimlico.io/v2/4663/rpc?apikey=… with the app's key; without a key, the public https://public.pimlico.io/v2/4663/rpc
Rate limit5,000 requests per minute with a key; 20 per minute per IP on the public endpoint
EntryPointv0.8, 0x4337084D9E255Ff0702461CF8895CE9E3b5Ff108

The API key ships in the page, so it is restricted on Pimlico's side: to the vault as the only contract, to the app's origin, with no sponsorship policy and a low spending cap. The vault rejects any operation with paymasterAndData, so the key cannot be used to sponsor gas. The app talks to Pimlico directly, not through a proxy of ours that would see users' IP addresses next to their operations.

Limits that matter:

  • Rate limit. One private action makes a few requests: a gas price, an estimate, the send, then receipt polls from every 2 seconds backing off to 5. On the public endpoint, several actions in a row from one IP can hit 20 per minute.
  • Validation gas. The app does not use the bundler's validation estimate, which is far above what a private transaction uses. It sets verificationGasLimit to its own 5,500,000 and takes only preVerificationGas from the bundler.
  • Gas price. The app reads it with pimlico_getUserOperationGasPrice, a Pimlico method, and pays 1.25 times the standard price.

Any ERC-4337 bundler that supports EntryPoint v0.8 can be used instead.

On this page