Technical Overview
Robinhood contracts, Base VRF, CCIP, and integration boundaries
Technical Documentation
Revision: Robinhood / three-plan referral specification, October 2026.
Repository boundary
This repository is the Next.js/Fumadocs documentation website. It implements documentation pages, a static search index, and a Gemini-powered chat route. It does not contain the project Solidity contracts, PHP main application, a verified ABI bundle, or deployment manifests for the described cross-chain integration.
The contract reference follows the supplied project specification. It distinguishes stated behavior from integration requirements and features carried forward as plans. Public contract addresses are omitted until their complete values and deployment versions are verified; do not use shortened addresses as configuration.
System
FOSNFT, Processor, Referral, and Verify are user-facing components on Robinhood Chain. The specified randomness design requests Chainlink VRF on Base using CCIP messaging. Authentication of cross-chain responses, supported lanes, fee funding, and deployed callback interfaces require verification against the final code.
References
| Section | Scope |
|---|---|
| Smart Contracts | Component boundaries and target parameters |
| FOSNFT & Processor | Mint, reserve, cycle, weighting, and payment rules |
| Referral | Actual specified function names and plan math |
| Verify | Certificate issuance, roles, and revocation |
| Free Mint | Confirmed cycle freebies versus planned Genesis campaign |
| Campaign | Carried-forward campaign design and funding constraints |
| Application | Wallet and state integration requirements |
| Security | Risks and required implementation checks |
| APIs | Implemented docs routes and main-app integration models |
| Network information | Mainnet/testnet IDs and registry references |
Documentation-site workflow
Use Node.js >=20.9 and the committed lockfile: npm ci, npx fumadocs-mdx, npm run dev. Validate with npx tsc --noEmit and npm run build. Inter is vendored with its license, so the production build needs no Google Fonts download. GEMINI_API_KEY enables real AI responses; without it, chat returns an explicit configuration error. Set credentials securely in the cloud/deployment environment, never in source control.