Production contracts

These are the current production contracts used for crypto-paired and stock-paired o1 Launchpad tokens on Base and Robinhood Chain, plus staking on both chains. The Base stock suite, plus Base and Robinhood stock-quote availability, were verified onchain on August 20, 2026. The other launch-suite addresses and connections were verified onchain on July 28, 2026. The staking deployment and fee configuration have a separate verification date below.

​

Base mainnet

Chain ID 8453. View the network on Basescan.

​

Crypto-paired launch suite

This is the active Base route for ETH and USDC pairs.

​

Stock-paired launch suite

This route has four registered Base Stock Tokens from a 13-asset catalog, free creation (nativeLaunchFee = 0), and new creation enabled. See Stock-paired launches for every catalogued address and its current registration status.

​

Base B20 protocol contracts

The factory checks activation of keccak256("base.b20_asset") before every B20 launch.

​

Uniswap and paired assets

​

Robinhood Chain

Chain ID 4663. View the network on Robinhood Chain Blockscout.

​

Crypto-paired launch suite

This is the active Robinhood route for ETH and USDG pairs.

​

Stock-paired launch suite

This route has 194 registered Robinhood Stock Tokens, free creation (nativeLaunchFee = 0), and new creation enabled. See Stock-paired launches for every paired-asset address.

​

Uniswap and paired assets

​

Staking

The staking contract is deployed at the same address on both production chains. Vault state, balances, and claims remain independent on each chain. The following mutable staking configuration is the same on both networks and was verified onchain on August 19, 2026: The fee is added to the vault’s reward budget and paid in the selected reward currency when the vault is created. The owner can update the fee rate and recipient for future vault creation, up to the contract’s 100% hard cap. If the configuration changes between review and submission, creation stops so the creator can review the updated amount. Fee changes cannot alter an existing vault, withdraw its accounted principal or rewards, or affect participant claims. There is one separately deployed staking contract on each supported chain. Individual vaults are records inside that contract, not separate deployments. See the staking guide for the complete user flow.

​

Governance and fee recipient

These addresses are the same on both production chains. The current owner controls configuration for future launches. The platform fee receiver receives the platform share of swap fees. Creation fees are currently zero on every available production route. Neither address can modify a completed token or remove its liquidity.

​

Verification links

Each address links to its chain explorer. Base’s native B20 addresses are also defined in the Base B20 specification, and the Uniswap addresses match the official Uniswap v4 deployment list. See the machine-readable deployment snapshot for normalized launch-suite addresses and current launch configuration values. The staking deployment and its dated live fee configuration are listed above.