PONS Integration — MVP

Assumption

FORGE integrates against PONS v2 on Robinhood Chain through the published factory/router/escrow contracts. Addresses and launch config IDs must be treated as deploy-time/runtime configuration, never copied permanently from this document.

Official docs reviewed: https://docs.ponsfamily.com/v2

As of the docs reviewed on 2026-10-08:

• PONS v2 starts launches on a bonding curve and automatically graduates to a permanently locked Uniswap v4 position.
• The factory + each launch curve expose enough events to reconstruct protocol state without relying on a PONS API.
• Creator/protocol fees are credited to an escrow and claimed by recipients.
• Public v2 launching is documented as gated at present; use canLaunch(address) rather than assuming launch access.
• PONS v2 audit work is documented as still in progress; FORGE must present integration risk honestly and keep the adapter upgradeable/configurable.

Why FORGE does not need a replacement launch contract

The PONS factory remains the actual launch mechanism. FORGE needs its own fee-recipient vault contract, not a copy of PONS launch logic.

At launch:

PONS creatorFeeRecipient = AgentFeeVault(agent)

Then:

PONS Fee Escrow
      |
      | claim by AgentFeeVault
      v
AgentFeeVault
  | platformFeeBps of gross (default 15%) -> FORGE platform fee address  [untouched by tip]
  | then callerTipBps of remaining pool (default 1%) -> msg.sender
  | rest of remaining pool -> Agent beneficiary/action destination

This keeps PONS economics canonical while making the FORGE platform fee auditable. The claim tip is carved from the beneficiary pool only. BPS values are read live from AgentFeeVaultFactory at claim time. See Fee keeper for profitability-gated auto-claims.

Launch configuration flow

Step A — Simulate / Compute ECA (no signature)

Button in Review & Launch (and CLI --dry-run / simulate):

1. read factory chain ID and compare expected Robinhood Chain ID
2. read canLaunch(user)
3. enumerate current enabled launch configs
4. read launch fee + approved pair assets
5. generate or accept a 32-byte PONS salt (namespaced to the creator wallet)
6. previewLaunchEconomics → pin expectedEconomics
7. AgentFeeVaultFactory.predictVault(agentId, owner, beneficiary) → vault ECA (owner = creator wallet)
8. PONS predictLaunchAddresses with full launch terms (including creatorFeeRecipient = vault ECA) → token ECA + curve ECA
9. return a LaunchSimulation object (addresses, salt, economics hash, fees, expiry) for the UI to display

Do not deploy the vault in this step. Do not send a transaction.

Step B — One-tx launch via ForgeLaunchRouter

1. Server builds unsigned calldata for ForgeLaunchRouter.launch(...) (or launchAndBuy overload) that:

- deploys the vault at the predicted CREATE2 address - calls PONS launch with creatorFeeRecipient set to that vault - optionally performs opening buy in the same call

1. User signs once
2. Indexer correlates VaultCreated + TokenLaunched from the same tx

Never cache launch config IDs forever. Read current list/config before every simulate. Re-simulate if any pinned input changes.

Forbidden: separate “deploy vault” tx then later “launch token” tx as the default creator path.

Factory event indexing

Minimum factory event:

event TokenLaunched(
  address indexed token,
  address indexed curve,
  address indexed deployer,
  address pairToken,
  uint256 launchConfigId,
  uint256 graduationThreshold
);

On event:

• insert tokens
• insert launches
• begin watching curve
• try to correlate pending launch intent by deployer + tx hash / metadata
• publish launch.created

Curve indexing

Use the exact ABI from the deployed PONS version. Persist all trade quantities from emitted values rather than recomputing from a requested amount because the finishing buy can be partially filled.

For each trade persist at minimum:

• token
• curve
• buyer/seller/recipient where emitted
• quote in/out
• token in/out
• base fee
• creator tax
• block/timestamp
• tx hash/log index

Use the on-chain quote/read methods for current displayed execution estimates. Opening snipe-tax behavior must be included in quotes when active; do not show a curve-only quote that differs from settlement.

Graduation

When graduation is detected:

• update launch status CURVE -> GRADUATING -> POOL
• resolve pool identifiers from PONS state/events
• switch quote/trade UI adapter from curve to graduated pool path
• continue a single chart series across both venues via Mobula TradingView datafeed (prefer mode=pool with curve then graduated pool address)
• buy/sell execution routing via Mobula swap quoting (Market data); pass poolAddress when known
• display source/phase boundaries on detailed analytics
• if Mobula quotes omit opening snipe tax, warn in UI and/or fall back to PONS on-curve quote for that window

Fee escrow integration

PONS documents an escrow with native and ERC-20 ledgers. The AgentFeeVault reference implementation expects an escrow interface like:

interface IPonsFeeEscrow {
    function claim() external;
    function claimToken(address token) external;
    function balanceOf(address recipient) external view returns (uint256);
    function balanceOfToken(address recipient, address token) external view returns (uint256);
}

The vault calls claim as itself, receives the asset, then immediately splits it.

Important:

• verify the production escrow ABI/address against the live PONS deployment before deployment
• do not use delegatecall
• vault owner (launching creator) can setBeneficiary / transferOwnership after launch
• factory admin cannot change vault beneficiary; platform fee BPS + tip + platform recipient are admin-editable on factory
• one vault per agentId (CREATE2 salt); no need to redeploy vault to migrate the fee wallet

FORGE CLI launch

The FORGE token is launched through the same PONS factory as creator tokens. Special treatment is only in FORGE's product DB:

• verified platform-token flag
• official Agent profile
• featured presentation

The chain launch remains normal and indexable.

CLI steps:

pnpm launch:forge --config ./launch/forge.json
 -> assert chain 4663
 -> factory.canLaunch(deployer)
 -> read enabled config
 -> preview economics
 -> predict/deploy official FORGE AgentFeeVault if used
 -> explicit typed confirmation
 -> launchToken / launch-and-buy router
 -> wait receipt
 -> parse TokenLaunched
 -> write receipt JSON locally
 -> call authenticated admin import endpoint OR run import script

Adapter config

RH_CHAIN_ID=4663
RH_RPC_HTTP_PRIMARY=
RH_RPC_HTTP_SECONDARY=
RH_RPC_WS_PRIMARY=
RH_RPC_WS_SECONDARY=
PONS_FACTORY_ADDRESS=
PONS_FEE_ESCROW_ADDRESS=
PONS_LAUNCH_AND_BUY_ADDRESS=
PONS_DEPLOYMENT_BLOCK=
PONS_DEFAULT_LAUNCH_CONFIG_ID=
PONS_DEFAULT_PAIR_TOKEN=

Do not commit production addresses until verified from official docs/deployment records.