RaidzATTENTION, WITH PROOF.
Open app

Pons V2 integration

Raidz is designed to launch and route $RAIDZ through Pons V2 on Robinhood Chain. Pons is an external protocol trust boundary: its factory, configuration, access rules, bytecode, economics, and audit state must be read fresh before a launch or value-bearing integration.

Integration responsibilities

The planned Pons adapter must:

  • resolve the official factory and singleton contracts;
  • enumerate enabled launch configurations;
  • read launch fee and maximum creator tax;
  • call canLaunch for the exact deployer;
  • call previewLaunchEconomics for the selected configuration and pair;
  • index launch, curve buy/sell, graduation, pool, fees, tax, buyback, vesting, and sweep events;
  • resolve per-token curve and post-graduation pool state;
  • handle quote refunds and partial fills around graduation;
  • fail closed when live state conflicts with cached state.

Phase-aware routing

Before graduation, token acquisition routes through the launch-specific bonding curve. After graduation, it routes through the registered Uniswap v4 pool. Near the boundary, cached state is unsafe: a transaction may cross phases or return unused quote assets.

Raidz funding code must quote and execute against current phase, enforce amount/slippage/deadline bounds, reconcile token and quote deltas, and never automatically retry an ambiguous transaction.

Read-only provenance registry

packages/domain/src/pons-v2-registry.ts pins:

  • Robinhood Chain ID 4663;
  • nine documented singleton addresses;
  • observed runtime bytecode sizes and SHA-256 hashes;
  • the ABI fragments required for factory, curve, hook, fee escrow, and buyback-vault reads;
  • deterministic hashes of those fragments.

This provides drift detection and attributable integration input. It is not a verified full ABI, security audit, launch approval, or substitute for a same-session chain read.

Launch gate

The twenty launch checks in Pons readiness gate must all be current. After configuration verification, the operator generates a fresh salt, predicts the token/curve addresses, prepares the canonical publication packet, simulates the exact transaction, signs through the approved project signer, and reconciles the receipt plus resulting factory state.

No launch transaction or $RAIDZ deployment has occurred.