Integration Checklist

A condensed, checkable summary of the developer guides. Work through every item that applies to your integration before going to production.

Network and deployments

• Enforce Robinhood Chain mainnet 4663 and testnet 46630 explicitly.
• Use a dedicated production RPC provider.
• Load all Raphael addresses from a versioned deployment manifest.
• Verify proxy implementations and administrative roles.
• Pin ABI versions to the deployed bytecode.

Tokens

• Resolve decimals, symbol and name from verified addresses.
• Treat symbols and logos as untrusted metadata.
• Define handling for fee-on-transfer, rebasing, pausable and blocklisted tokens.
• Maintain an explicit connector-token policy for routing.

Quotes and transactions

• Compare direct and bounded multi-hop routes.
• Quote against current onchain state.
• Apply user-visible slippage and minimum-output limits.
• Set transaction deadlines.
• Simulate before sending.
• Handle replacement, dropped and reverted transactions.
• Show explorer links and actual receipt outputs.

Aggregators

• Index every supported Raphael factory and pool class.
• Preserve factory, pool class, fee and token direction on every route edge.
• Tag quotes with a source block and expiry.
• Validate routers and pools against the current deployment allowlist.
• Test basic, concentrated and mixed routes supported by the deployment.
• Report actual receipt outputs rather than the quoted amount.

Liquidity

• Validate pool type, factory and gauge status.
• Preserve token ordering and decimal scaling.
• Validate concentrated ticks and current range state.
• Explain staked-vs-unstaked fee consequences.

Launchpads

• Commit the graduation threshold and asset accounting before launch.
• Freeze the bonding curve before migration begins.
• Match or explicitly disclose the difference from the final curve price.
• Create and seed the pool atomically where possible.
• Make retries idempotent and reject duplicate graduation.
• Validate any pre-existing pool before depositing.
• Publish LP burn, lock, vesting or treasury control.
• Emit a canonical graduation record with final amounts and addresses.
• Disable curve trading after the Raphael pool is confirmed live.

Security and operations

• Minimise approvals and support revocation.
• Rate-limit public endpoints.
• Cache non-critical metadata without caching transaction-critical state too long.
• Monitor contract events, RPC health and indexer lag.
• Maintain incident messaging and a safe method to disable affected UI actions.
• Never imply an upstream audit automatically covers Raphael's fork or deployment.