Deployments

NetworkCopy Anchor Link

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 addressesCopy Anchor Link

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

Pons V2Copy Anchor Link

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

Shared infrastructureCopy Anchor Link

Deterministic addressesCopy Anchor Link

Every zerotrace contract is 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 the zerotrace addresses above are fixed before deployment. ZERO's and the curve's addresses are not: they are set by Pons.

Where ZERO tradesCopy Anchor Link

ZERO trades in two places over its life, both run by Pons:

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 harvester make them themselves on the next trade if nobody else has.

The graduated pool's PoolKey:

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 harvester 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.

BundlerCopy Anchor Link

Private actions (send, sell, unshield) 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:

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.