Robinhood Chain · Degraded
Chain details
Chain ID
4663
Latest observed block
Unavailable
Observation time
Unavailable

How OPAIR works

Documentation

OPAIR is building option-pegged memecoins on Robinhood Chain: every launch is a real Uniswap v4 market paired to one curated option contract: a strike, an expiry, a countdown. Here is exactly how it works and where it stands today.

The product

Memecoins with an expiration date.

Every OPAIR launch is a fixed-supply memecoin paired to one curated option contract: an underlying stock, a call or a put, a strike, an expiry. The token is designed to be pegged to that option contract's price: when the option moves, the token moves with it.

That pairing gives every launch two properties no plain memecoin has. An expiration date: the paired contract's expiry, a countdown every holder can see. And amplified volatility: options move in multiples of their underlying, so a token pegged to an option inherits violent swings around the strike, into expiry, and through the underlying's price action.

The peg mechanism

In active build

The peg is maintained by two automated mechanisms working off a live reference price for the paired option contract:

  • Option price oracle. The paired contract's market price streams on-chain as the reference level the peg targets.
  • Automated supply management. Supply-side pressure (contraction as the reference falls, expansion as it rises) pulls the token's market price back toward the option's price.
  • Reference-level market-making. Liquidity concentrates around the reference level and re-centers as the option moves: tightest near the strike, into expiry.

When the paired contract reaches expiry, the pairing resolves against the option's final settlement print, and the token's countdown ends with it. New contracts list, new pairs launch, and the experiment rolls forward.

This mechanism is what OPAIR is built to ship: it is the product design, described as designed. It is in active build and not live on-chain yet.

Launch mechanics

Every launch is one transaction. The launchpad does all of this atomically: the same economics, every time.

  1. Fixed-supply mint

    One transaction mints a 1,000,000,000-token ERC20 to the launchpad. Supply is fixed at launch: nobody picks it, and it can never change.

  2. Genesis curve pool

    A hooked, single-sided bonding-curve pool opens over ticks [180000, 200000], initialized at the top tick. Genesis price ≈ 2.0612e-9 ETH per token, which is a starting market cap of ≈ 2.06 ETH, identical for every launch. Nobody picks a price.

  3. Locked vanilla pool

    A hookless full-range pool is seeded with half the launch buy and locked forever: the launchpad contract has no remove function.

  4. Creator's first buy

    The creator's mandatory first buy routes through the SwapRouter, so the token has a trade, and aggregator indexing, from block one.

  5. Pairing recorded

    The curated option level (underlying, call or put, strike, expiry) is recorded on-chain against the new token in the PairingRegistry.

  6. Metadata published

    The pairing record is published to the MetadataRegistry as pairedSeries metadata, so explorers and indexers can read it from block one.

Contract stack

Live on Robinhood Chain (chainId 4663) and Sourcify-verified. Addresses are checksummed. Verify on Blockscout before you interact.

  • LaunchpadOne-transaction launches: mint, both pools, first buy, pairing record.
    0x93D84a0e4B7229b258991E90a093cfEd9B69e1C6
  • LaunchpadHookUniswap v4 hook enforcing the single-sided bonding curve.
    0x40822718352e71Be30A1880644BF6Cc3003fD040
  • SwapRouterRoutes the creator's first buy and every aggregator-style swap.
    0xaB242fC77284f256eACEca83fAAeecec4506D2C4
  • PairingRegistryOn-chain record of each token's curated option level.
    0xaf4dACe6B281873a7f7Ec288927F06edf0daE943
  • MetadataRegistryPublishes pairedSeries metadata for explorers and indexers.
    0xDE4796132ECD6c58236AACDDc106fc36d1F5878c
  • Uniswap v4 PoolManagerSingleton holding every pool's state and liquidity.
    0x8366a39CC670B4001A1121B8F6A443A643e40951
  • StateViewRead lens over PoolManager slot0, liquidity, and positions.
    0xf3334192d15450cdd385c8b70e03f9a6bd9e673b
  • V4QuoterOff-chain quote simulation for swaps before they land.
    0x8Dc178eFB8111BB0973Dd9d722ebeFF267c98F94
  • Permit2Canonical signature-based token approval, shared across chains.
    0x000000000022D473030F116dDEE9F6B43aC78BA3

Fees

1%LP fee on every swap, in both pools
70%of accrued fees to the creator
30%of accrued fees to the platform

The split is enforced by the launchpad contract, not by policy: the same 1% and the same 70/30 on every launch, forever.

The pairing board

The pairing board is the curation surface behind every launch. Underlyings are curated. Expiries are select dates: monthlies, quarterlies, and LEAPS. Strikes are the important levels only: round increments near spot. Live option pricing and implied volatility stream in from the market-data API routes.

The board is display-only. It informs the level recorded at launch; it is not a trading venue, and its quotes are reference data, not offers.

Reading the chain

Pool identity
poolId = keccak256(PoolKey): every pool is the hash of its key.
Price
price = 2^192 / sqrtPriceX96²: ETH per token, straight from slot0.
Event-sourced lists
Launches and pairings rebuild from Launched and MetadataSet logs. No indexer required.
Instant paint
Reads are cached in localStorage so revisits render immediately, then revalidate against the chain.

OPAIR is an experiment. Nothing on this page is investment advice, and nothing launched here is a derivative, an option, or a security.