Hood League Docs
DOCS v1.2 · PRE-LAUNCH Beta v2.1 Back to site ↗
HOOD LEAGUE DOCUMENTATION

Fantasy markets.
Documented properly.

Hood League is a pre-launch fantasy-market competition experience designed for Robinhood Chain. Players build a five-asset lineup, follow real market inputs, and compete through a league layer that turns market movement into gameplay.

NETWORKRobinhood ChainEthereum L2
ROUND FORMAT5 assetsDaily competition model
DATALive inputsMulti-source market feed
STATUSPre-launchProduct preview
01 · PRODUCT STATUS

What is live, what is preview, and what is planned.

The documentation separates working functionality from illustrative UI and future protocol work. This is intentional: market data can be live even when league scoring or token functionality is still pre-launch.

LIVE

Working production functionality that can be verified today.

PREVIEW

Product behavior or UI demonstrated before production settlement exists.

PLANNED

Roadmap functionality that is not deployed and must not be represented as live.

LIVE

Market data pipeline

Hood League fetches external market data through a server-side API and refreshes the interface on a short interval.

LIVE

EVM wallet discovery

Injected wallets can be detected and connected. The UI can request Robinhood Chain as the active network.

PREVIEW

League gameplay

Drafting, player profiles, leaderboards and round screens are product previews. Beta v2.1 values are not live competition results.

PLANNED

Public scoring layer

Final round snapshots, scoring rules, anti-manipulation controls and public league settlement will be specified before launch.

PLANNED

$LEAGUE

The utility token is not live. Final contract address, Pons V2 launch configuration and onchain parameters will be published at launch.

PLANNED

Native mobile apps

iOS and Android are roadmap items. Current mobile screens represent the intended interface direction.

02 · SYSTEM ARCHITECTURE

One product, three layers.

Hood League is intentionally separated into the product experience, market-data infrastructure, and the Robinhood Chain / future contract layer.

Design principle

The browser does not need to know how each upstream provider formats data. Hood League normalizes external inputs into one internal asset schema before rendering them.

03 · PRODUCT BOUNDARIES

What Hood League does — and does not do.

Clear negative definitions reduce ambiguity. Hood League should be explicit about where the game ends and custody, trading, market infrastructure or investment products begin.

DOES

Read and normalize market inputs for supported assets.

DOES

Turn published market performance into a fantasy-league score.

DOES NOT

Buy, sell, custody or transfer an asset merely because a player drafts it.

DOES NOT

Use $LEAGUE holdings, cosmetics or profile status to improve market-return scoring.

DOES NOT

Invent replacement prices when an accepted scoring source is unavailable.

DOES NOT

Treat Stock Tokens as ownership of the underlying shares they reference.

Core trust principle

Every production round should be reproducible from its asset identities, accepted source snapshots, normalization rules and scoring specification.

04 · DAILY ROUNDS

The core game loop.

The intended round model is simple enough to understand in seconds and strict enough to become deterministic once public scoring is finalized.

01

Draft

Choose exactly five supported market assets before the round lock.

→
02

Lock

The round records a defined asset set and pricing boundary.

→
03

Track

Market movement is observed during the round window.

→
04

Score

Returns are converted into a deterministic league result.

→
05

Rank

Players are ordered by the final round score.

NON-NEGOTIABLE

Market performance stays market performance.

$LEAGUE, cosmetics, access passes or profile status must not change an asset's market return inside the scoring formula. Hood League is designed to avoid pay-to-win scoring.

PRE-LAUNCH

Final scoring is not published yet.

The live site currently demonstrates the loop with illustrative scores. Round start/end snapshots, tie-breaking, stale-feed behavior and edge cases will be published before public competition goes live.

05 · ASSET UNIVERSE

Multiple markets, one draft.

Hood League is designed around a mixed market universe rather than a single asset class.

ST

Stock Tokens

Robinhood-issued Stock Tokens may provide the equity-reference layer where supported and legally available.

Example class: U.S. equity references
₿

Crypto

Major crypto assets can provide continuously moving market inputs and a complementary risk profile.

Example class: BTC · ETH · DOGE
RC

Robinhood Chain assets

Selected independent tokens deployed on Robinhood Chain may be included when contract identity and liquidity can be verified.

Contract-first identification
Asset inclusion ≠ endorsement

Displaying an asset does not mean Hood League recommends, sponsors, guarantees, or is affiliated with that asset or issuer.

06 · CANONICAL ASSET REGISTRY

Ticker is display copy. Identity is canonical.

Hood League should never trust a symbol alone. Every production asset resolves to a canonical internal record before it can appear in a scoring universe.

IDENTITYassetIdsymbolassetType
ONCHAINchainIdcanonicalContractdecimals
DATApriceSourcenormalizationverifiedAt
ROUNDstatusscoringEligiblefailurePolicy
Conceptual canonical asset record
{
  "assetId": "stock-token:AAPL",
  "symbol": "AAPL",
  "assetType": "stock-token",
  "chainId": 4663,
  "canonicalContract": "verified-from-official-registry",
  "priceSource": "robinhood",
  "normalization": "underlying-mid × currentMultiplier",
  "scoringEligible": true
}
Contract-first for onchain tokens

Independent Robinhood Chain assets are matched by exact configured contract address. A duplicate ticker or lookalike token must never inherit another asset's identity.

07 · MARKET DATA

How the live board gets its numbers.

The current website uses a server-side aggregation endpoint. Each market category has a defined source and failure behavior.

STOCK TOKENSRobinhood REST/assets + /prices/{symbol}
→Normalizemid-price × multiplier
CRYPTOCoinGeckoUSD + 24h change
→Normalizeshared schema
ONCHAIN TOKENSDEX Screenerexact contract address
→/api/marketHood League feed

Stock Token price normalization

Robinhood's REST price endpoint returns the raw underlying-equity bid/ask. The REST value is not multiplier-adjusted. Hood League therefore reads currentMultiplier from /assets and applies it when a Stock Token quote is available.

Token-equivalent price ((bid + ask) ÷ 2) × currentMultiplier Do not apply the multiplier a second time to an onchain Chainlink feed that already incorporates it.
CategoryPrimary sourceChange windowFailure behavior
Stock TokensRobinhood Stock Token APIvs previous U.S. regular closeDisplay fallback may be used; otherwise “—”
Major cryptoCoinGecko24 hours“—” when unavailable
Selected onchain tokensDEX Screener24 hoursOnly exact configured contracts are accepted
Current refresh behavior

The UI requests a fresh Hood League market snapshot roughly every 20 seconds. Upstream providers may use their own caching windows, so “live” means recently refreshed market data, not tick-by-tick exchange execution data.

08 · PRICE NORMALIZATION

Corporate actions cannot become game events.

Splits and other multiplier changes can alter the relationship between a Stock Token and its referenced security without representing economic market performance. Hood League must normalize these changes before scoring.

01

Resolve asset

Load canonical Stock Token metadata and the multiplier valid at the snapshot boundary.

→
02

Normalize price

Convert raw REST underlying quotes to the token-equivalent value when required.

→
03

Detect changes

Record multiplier/corporate-action changes across the round window.

→
04

Score economics

Compare economically equivalent start/end values rather than raw unadjusted numbers.

No double multiplier

If an accepted onchain feed already incorporates the Stock Token multiplier, Hood League must not apply that multiplier again. Each source adapter owns one documented normalization path.

10 · SCORING SPECIFICATION

Deterministic by design.

The production scoring rules will be versioned and published before public leagues. The current candidate is intentionally simple: equal-weight the normalized returns of the five drafted assets.

Asset return rᵢ = (Pᵢ,end ÷ Pᵢ,start) − 1 P values are canonical, normalized round snapshots.
Candidate lineup score · spec v0.1 Score = (r₁ + r₂ + r₃ + r₄ + r₅) ÷ 5 Equal weight. No $LEAGUE modifier. Not yet live for public competition.
1Lock boundaryOne exact start timestamp and accepted source snapshot per asset.
2NormalizationApply the asset adapter's versioned corporate-action and source rules.
3Return calculationCalculate the same percentage-return function for all five picks.
4Equal-weight aggregationAverage the five normalized returns under the candidate v0.1 specification.
5FinalizationSettle only when every required snapshot passes freshness and integrity checks.
Specification status: preview

The formula above is the current candidate specification and is included to make product design concrete. Hood League may revise it before public leagues; any production change must create a new explicit scoring-spec version rather than silently changing active rules.

11 · ROUND FINALIZATION

Fail closed, then rank.

A round should not finalize merely because the clock reached its end. The scoring pipeline first validates the accepted snapshots and then publishes the result.

01

Freeze

Record the expected end boundary and freeze the lineup state.

02

Validate

Check source, timestamp, freshness, multiplier and canonical asset identity.

03

Compute

Run the versioned scoring specification against accepted snapshots.

04

Publish

Store the score, scoring-spec version and data provenance needed to reproduce it.

Missing end data

The proposed policy is to delay finalization for the affected round rather than substitute an unapproved feed or fabricate a price. A production timeout/escalation rule will be published before live leagues.

12 · ROBINHOOD CHAIN

Network configuration.

Robinhood Chain is an Ethereum-compatible Layer-2 network using ETH as its native gas token. Hood League's production network target is Robinhood Chain mainnet; development should be validated on testnet first.

MAINNET

Robinhood Chain

Chain ID
4663
Hex
0x1237
Gas
ETH
Explorer
Blockscout
TESTNET

Robinhood Chain Testnet

Chain ID
46630
Gas
ETH
Purpose
Integration testing
Explorer
Testnet explorer
Production RPC

Robinhood's public RPC endpoints are rate-limited and not recommended for production. Robinhood documentation recommends a provider such as Alchemy for production infrastructure.

13 · WALLETS

Self-custody by default.

Hood League connects to EVM-compatible wallets. Users keep custody of their keys and explicitly sign any future onchain transaction.

CURRENT

Injected wallet connection

The landing page discovers MetaMask and compatible injected providers using modern EVM wallet discovery plus a legacy provider fallback.

RULE

No seed phrase. Ever.

Hood League should never request a seed phrase, private key, or wallet recovery secret. Connection and signatures happen inside the user's wallet.

Switch to Robinhood Chain
const ROBINHOOD_CHAIN_ID = '0x1237'; // 4663

await window.ethereum.request({
  method: 'wallet_switchEthereumChain',
  params: [{ chainId: ROBINHOOD_CHAIN_ID }]
});

If the network is missing, an EIP-1193 wallet can be asked to add Robinhood Chain using chain ID 4663, ETH as the native currency, and the official network/explorer endpoints.

14 · STOCK TOKENS

Use the correct model and terminology.

Robinhood Stock Tokens are standard ERC-20 tokens issued by Robinhood Assets (Jersey) Limited. They provide economic exposure to referenced securities but do not grant legal or beneficial ownership in the underlying issuer or shares.

STANDARDERC-2018 decimals
PRICINGChainlinkPer-asset onchain feeds
UI SCALINGERC-8056uiMultiplier()
REST DATARHJ APIRead-only endpoints

The multiplier matters

Corporate actions such as stock splits can change the shares-per-token relationship. Robinhood exposes currentMultiplier in its Stock Token asset metadata and an onchain uiMultiplier() mechanism. The raw wallet balance can remain unchanged while the UI amount and reference price relationship change.

Normalize a REST Stock Token quote
const bid = Number(quote.bid);
const ask = Number(quote.ask);
const multiplier = Number(asset.currentMultiplier || 1);

const underlyingMid = (bid + ask) / 2;
const tokenEquivalentUsd = underlyingMid * multiplier;
Jurisdictional restrictions

Stock Tokens are not available to every person or jurisdiction. Hood League's display or fantasy use of a Stock Token reference does not override the issuer's legal, transfer, trading, or geographic restrictions.

09 · DATA INTEGRITY

Prefer explicit failure over fake certainty.

A fantasy product is only credible if its data behavior is predictable. Hood League should never silently replace missing live market data with random or simulated prices.

01

Contract-first onchain identity

Onchain tokens should be resolved from configured contract addresses, not ticker text alone.

02

No stale masquerading as live

If a required feed fails and no approved fallback exists, render an unavailable state instead of fabricated data.

03

Timestamp every snapshot

Store source timestamps and the Hood League fetch timestamp so scoring can be audited later.

04

Separate display from scoring

A UI fallback can keep a market board readable without automatically becoming an accepted scoring source.

16 · $LEAGUE

Utility around the game, not inside market performance.

$LEAGUE is a planned Hood League utility token. It is not live today, and no contract address should be trusted until Hood League publishes one at launch.

♕

Premium leagues

Access to selected seasonal or specialized league formats.

+

Create leagues

Planned utility for player- or community-created competitions.

◇

Player identity

Cosmetic and profile features that do not alter market scoring.

◎

Community choice

Potential product-focused participation around league formats and supported experiences.

PLANNED SUPPLY1,000,000,000LEAGUE
PRIVATE SALE0%planned
PRE-LAUNCH TEAM0%planned
STATUSPRE-LAUNCHno official CA yet
No investment promise

$LEAGUE is not described as equity, revenue share, guaranteed yield, guaranteed appreciation, or a promise of financial return.

17 · PONS V2

Planned launch lifecycle.

The current launch plan targets Pons V2 on Robinhood Chain. Pons V2 starts launches on a bonding curve and creates the Uniswap v4 pool only at graduation.

01

Create

The fixed supply is minted to the launch curve under a selected launch configuration.

→
02

Curve

Users buy and sell against the bonding curve. Price changes with curve utilization.

→
03

Graduate

Once the configured sellable allocation is exhausted, graduation can execute automatically.

→
04

Pool

A Uniswap v4 pool is created and its liquidity position is permanently locked by the protocol.

Configuration, not a magic number

Graduation is controlled by the selected Pons V2 launch configuration, including the graduation threshold and pool parameters. Hood League will publish the final selected configuration and transaction details at launch rather than presenting an assumed fixed ETH threshold.

18 · DEVELOPER API

Hood League market snapshot.

The current site exposes one internal/public-read endpoint used by the landing page and Beta v2.1 experience to consume a normalized market snapshot.

GET/api/marketJSON · cached at the edge
Response shape
{
  "ok": true,
  "assets": {
    "AAPL": {
      "symbol": "AAPL",
      "price": 0,
      "change": 0,
      "asOf": "ISO-8601 timestamp",
      "source": "Robinhood Stock Token API",
      "multiplier": 1,
      "changeWindow": "vs previous U.S. regular close"
    }
  },
  "fetchedAt": "ISO-8601 timestamp",
  "refreshSeconds": 20
}

The numeric values above are schema placeholders, not quoted market prices.

19 · CODE EXAMPLES

Consume the Hood League feed.

Fetch a normalized asset snapshot
const response = await fetch('/api/market', { cache: 'no-store' });
const market = await response.json();

const asset = market.assets.AAPL;

if (asset?.price) {
  console.log(asset.price, asset.change, asset.source);
}
Fail closed in the UI
function displayPrice(asset) {
  if (!Number.isFinite(asset?.price)) return '—';
  return new Intl.NumberFormat('en-US', {
    style: 'currency',
    currency: 'USD'
  }).format(asset.price);
}
15 · FUTURE CONTRACTS

Onchain only where it improves trust.

Hood League should not put every UI interaction onchain. Future contracts should be used where public verification, ownership or settlement materially improves the product.

PLANNED

League Registry

Canonical league configuration and creator/league identifiers where public ownership matters.

PLANNED

Round Settlement

Commit or attest finalized round results after the offchain scoring pipeline reaches deterministic output.

PLANNED

$LEAGUE Utility

Token-aware access, creation or identity functions after the official token exists.

Testnet first

Any Hood League contract should be deployed and exercised on Robinhood Chain Testnet before mainnet. Contract addresses must be verified publicly before users are asked to sign transactions.

20 · SECURITY

Security model.

01

Self-custody. Wallet keys remain with the user. Hood League does not need private keys or seed phrases.

02

Explicit chain validation. Transaction-enabled features should verify chain ID before requesting a signature.

03

Contract verification. Official contract addresses must be published from Hood League-owned channels and verified on the relevant explorer.

04

Data provenance. Market snapshots should record source, timestamp and normalization path.

05

No fake fallback data. Missing sources should degrade to an unavailable state rather than random prices.

06

Audit status is explicit. Hood League should never imply smart contracts are audited until an audit has actually been completed and published.

21 · KNOWN LIMITATIONS

Things the current product cannot promise.

Pre-launch documentation should describe constraints as clearly as capabilities. These limitations are expected to change as production infrastructure is completed.

Market data is not tick execution

The website refreshes normalized snapshots on an interval. Provider caching and network latency can make display data differ from an exchange's latest trade.

Preview rankings are not live results

Sample scores, ranks and leaderboard entries are product demonstrations until the production scoring layer is active.

Wallet connection is not custody

Connecting a wallet only exposes permitted account/network information. Hood League does not receive the wallet's private key.

Token parameters remain provisional

$LEAGUE supply/launch parameters shown before deployment are project plans, not verified onchain facts.

External dependencies can fail

Robinhood APIs, crypto data providers, RPC infrastructure, sequencer availability and third-party protocols can become unavailable.

Asset eligibility can change

Legal availability, token controls, liquidity or data quality may cause an asset to be unavailable for a future round.

23 · GLOSSARY

Key terms.

Account Abstraction

Programmable wallet infrastructure, commonly ERC-4337, enabling features such as batching, policies and gas sponsorship.

Bonding Curve

An automated pricing mechanism where token price changes as curve reserves and sold supply change.

Chain ID

The numeric identifier wallets use to distinguish EVM networks. Robinhood Chain mainnet is 4663.

currentMultiplier

Robinhood Stock Token metadata used to account for corporate-action scaling between raw underlying price and token-equivalent UI value.

Graduation

The Pons V2 transition from bonding-curve trading to a Uniswap v4 pool after the configured curve sells out its tradable allocation.

RPC

The JSON-RPC interface used by wallets and applications to read blockchain state and submit transactions.

Self-custody

A model where the user controls the wallet keys needed to authorize transactions.

Stock Token

A Robinhood-issued ERC-20 tokenised debt security providing economic exposure to a referenced security without underlying share ownership rights.

24 · CHANGELOG

Documentation changes are product changes.

v1.2

Trust & scoring pass

Added status vocabulary, product boundaries, canonical asset registry, corporate-action normalization, candidate scoring spec v0.1, round finalization and known limitations.

v1.1

Robinhood Chain documentation pass

Added Stock Token model, market API, wallet/network architecture, $LEAGUE plan and security sections.

25 · OFFICIAL SOURCES

Primary references.

Hood League documentation should treat protocol and network documentation as versioned dependencies. These links are the primary sources used for the current documentation pass.

LAST UPDATEDSeptember 11, 2026

Documentation reflects the current pre-launch Hood League product and public protocol documentation available at the time of this revision.