HyperSpeed protocol

Architecture decision

Pons V2 graduates into a Uniswap V4 pool with a shared fee hook. Official Uniswap deployment records do not list HyperEVM, so copying that exact stack would require launching and maintaining a new V4 DEX—and generic trackers would not automatically treat it as HyperSwap.

The production-safe first release uses HyperSwap V3, whose contracts and public subgraph are already live on HyperEVM. It preserves permanent liquidity and a 1% pool tier, but the optional creator curve bonus ends at graduation. A future V4 adapter can be introduced as a new immutable protocol version after an audited and indexed V4 venue exists.

Contract topology

HyperEVM dependencies

All production addresses must be checked with eth_getCode, chain ID 999, explorer verification and a forked integration test before deployment.

Fee policy

The 0.0005 HYPE creation fee is a low-friction anti-spam cost, not complete bot protection. Pair exact-value validation with wallet-aware API limits, metadata upload limits and monitoring. V3 fees accrue in both pool assets; the MVP distributes them as collected instead of forcing a manipulable token-to-HYPE swap. Never put fees in ERC20._update.

Launch lifecycle

MVP config 1 is the only public choice: graduation at 190 HYPE, displayed as an approximate $10K tier. Config 2 is fully specified at 1,900 HYPE but admin-disabled until the new platform has operating history. There is no USDT threshold and no price oracle. A timestamped HYPE/USD price is display-only; changing HYPE prices never change an existing launch.

1. PreviewFrontend reads enabled config and computes expectedEconomics across every owner-controlled term.
2. CreateOn a big block, the factory verifies the 0.0005 HYPE fee, initial-buy bounds and economics digest, then deploys clones and initializes the canonical V3 pool.
3. TradeCurve applies conservative rounding, quote-side fees, deadlines, slippage bounds and partial-fill refunds.
4. SweepAt the exact HYPE threshold, curve closes and atomically transfers reserved token and net HYPE into graduation custody.
5. SeedPermissionless, retryable V3 manager wraps HYPE, mints a full-range NFT into the pre-initialized pool directly to the locker and sweeps dust.
6. OperateAnyone harvests both pool assets to escrow. The position NFT and principal have no withdrawal path.

Frontend integration

The checked-in UI isolates wallet and contract work behind lib/protocol.ts. Configure audited addresses, then implement the adapter with viem or wagmi.

interface ProtocolAdapter {
  quoteInitialBuy(configId, hypeIn, bonusBps, slippageBps): Promise<Quote>
  quoteBuy(token, hypeIn, slippageBps): Promise<Quote>
  quoteSell(token, tokenIn, slippageBps): Promise<Quote>
  launchToken(input, payment?: LaunchPayment): Promise<TxHash>
  buy(token, hypeIn, minOut, deadline): Promise<TxHash>
  sell(token, tokenIn, minOut, deadline): Promise<TxHash>
  graduate(token): Promise<TxHash>
  claimFees(token): Promise<TxHash>
}

Indexer & API

RPC is a source of truth, not a scalable product database. Run a reorg-safe event indexer with a finality buffer, idempotent upserts and periodic reconciliation.

Primary events: TokenLaunched, Trade, GraduationSwept, PoolCreated, FeesCredited, FeesClaimed and policy/config updates.

Metadata & listings

Store name, symbol, metadataURI, logoURI and the metadata content hash onchain. Pin the canonical JSON and image to at least two IPFS providers before launch; the factory should reject mutable HTTP-only metadata.

Bridge routing

Use OpenSea as the primary bridge-and-swap surface because it supports cross-chain token swaps and HyperEVM. HyperSpeed does not custody bridge funds or add a bridge fee. The public page links users to OpenSea today; production can request an OpenSea Swap API quote through a backend-only route so the API key is never exposed in the browser.

Deployment gates

• 100% branch and invariant coverage for curve math, fees, caps and lifecycle states
• Fuzz buy/sell round trips across wei boundaries, partial fills and max values
• Assert config 1 is enabled at 190 HYPE, config 2 is disabled at 1,900 HYPE, and creation requires exactly 0.0005 HYPE plus the initial buy
• Keep ordinary trade paths below HyperEVM's current 2M fast-block gas limit; benchmark launch and pool seeding on 30M big blocks
• Fork-test that the execution salt cannot be predicted early enough to front-run canonical pool initialization
• Fork test against exact HyperSwap V3 factory, position manager, router and WHYPE
• Prove the locker cannot transfer the NFT or call decreaseLiquidity
• Reentrancy tests with hostile creator recipient, ERC-20 and fee receiver contracts
• Keep the OpenSea API key server-side and test route expiry, provider disclosure, minimum output and Jumper fallback
• Two independent deploy rehearsals with address and runtime-bytecode comparison
• Independent audit, remediation, re-audit and public verified-source release
• Canary mainnet launch with capped preset and monitored keeper before opening creation

Risk register