FOS LogoFOS Documentation
FOS Protocol

Platform Infrastructure

Robinhood user transactions and Base randomness integration

Platform Infrastructure

Networks

User-facing FOSNFT, Processor, Referral, and Verify interactions belong on Robinhood Chain, not Base. Base serves the specified VRF randomness integration, with CCIP transporting cycle requests and results.

NetworkChain IDNative currencyRole
Robinhood Chain4663ETHUser-facing project network
Robinhood Chain Testnet46630Test ETHSeparate testing network
BaseEnvironment-specificETHVRF service side of the specified cross-chain design

The Robinhood IDs, currency, and URLs below are corroborated by the public ethereum-lists network registry, with a separate testnet entry. This corroborates network metadata; it does not verify FOS deployments or CCIP support.

Verify the selected environment and live RPC chain ID before signing. Never reuse Base or Base Sepolia addresses for a Robinhood transaction. The Base environment used by the VRF integration must be confirmed separately.

ETH pricing and gas

The displayed dollar values are nominal product labels. On-chain ETH prices and cycle settings are the transaction source of truth. Ordinary mints require the exact configured price; free positions require zero purchase value. Network gas still applies. ETH remains volatile, and neither fixed gas costs nor USD-equivalent awards are guaranteed.

Wallet access

Use an EVM wallet configured for the correct Robinhood network. MetaMask and Coinbase Wallet are documented integration targets; connector behavior must be verified in the deployed main application. This Next.js repository hosts documentation and an AI assistant, not the minting application itself.

The interface does not need a user's private key. Contracts nevertheless hold cycle funds, reserved free-position contributions, and deferred payments according to their rules. An interface described as non-custodial does not mean that funds never enter a contract.

Cross-chain visibility

Show Robinhood cycle status and transaction receipts separately from Base VRF and CCIP delivery status. A successful last-mint receipt is not evidence that the remote random result has arrived or that the allocation transaction has completed.

On this page