FOS LogoFOS Documentation
Technical Docs

Smart Contracts Overview

Separate minting, cycle processing, referral, and certificate contracts

Smart Contracts

Contract suite

ContractResponsibilitySpecified network
FOSNFTNFT mint, purchase payment, admin balance, free-collectible reserveRobinhood
ProcessorAuthorized collectible registration, cycle state, selection, allocationsRobinhood
ReferralRegistration, plans, upgrades, and direct-referral paymentsRobinhood
VerifySeparate ERC-721 certificates, origin registry, validity statusRobinhood
VRF/CCIP integrationCarry cycle requests to Base and return VRF resultsRobinhood and Base

Only FOSNFT may register collectible mint records in Processor. Referral is independent of both contracts. Verify is optional and may be connected to FOSNFT and Referral; Processor has no direct Verify connection in the supplied structure.

Three independent collection types

CollectionType IDNominal priceAdmin feeAdmin per paid mintPool contribution per collectibleFull 500-collectible pool
Buddy3$35%$0.15$2.85$1,425
Samurai13$133%$0.39$12.61$6,305
Noble25$252%$0.50$24.50$12,250

Dollar amounts describe the product model, not a dollar-denominated contract balance or guaranteed allocation. Payments and allocations use native ETH. Read the configured on-chain price before sending a transaction; the production USD-to-ETH conversion policy is not supplied in the contract specification.

All three target 500 collectibles, with 17 selected collectibles and 50/30/20 group allocation. There is no specified 100-cycle lifetime cap. Only the initial weights and price labels are described here; per-cycle stored settings and current on-chain prices control execution.

Standards and authority

NFT/certificate documentation uses ERC-721. Do not infer ERC-721A, ERC-1155, UUPS upgradeability, timelocks, or audit status from older drafts. Referral owner controls include prices, split basis points, admin wallet, and Verify connection. Verify owner controls include approved minters, origin types, URI configuration, admin wallet, and revocation.

Deployment status

Robinhood Chain ID 4663 is reported by the supplied specification and corroborated by the public network registry. The specification provides incomplete addresses for some components and does not supply the final Base-side bridge deployment. Accordingly this reference does not publish operational FOS contract addresses, ABIs, RPC credentials, or callback selectors. The named functions in individual pages are specification references, not a replacement for a verified ABI.

Genesis allowlist and growth campaign contracts remain design material in the roadmap, not confirmed members of this deployed four-contract suite.

On this page