Market data pipeline
Hood League fetches external market data through a server-side API and refreshes the interface on a short interval.
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.
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.
Working production functionality that can be verified today.
Product behavior or UI demonstrated before production settlement exists.
Roadmap functionality that is not deployed and must not be represented as live.
Hood League fetches external market data through a server-side API and refreshes the interface on a short interval.
Injected wallets can be detected and connected. The UI can request Robinhood Chain as the active network.
Drafting, player profiles, leaderboards and round screens are product previews. Beta v2.1 values are not live competition results.
Final round snapshots, scoring rules, anti-manipulation controls and public league settlement will be specified before launch.
The utility token is not live. Final contract address, Pons V2 launch configuration and onchain parameters will be published at launch.
iOS and Android are roadmap items. Current mobile screens represent the intended interface direction.
Hood League is intentionally separated into the product experience, market-data infrastructure, and the Robinhood Chain / future contract layer.
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.
Clear negative definitions reduce ambiguity. Hood League should be explicit about where the game ends and custody, trading, market infrastructure or investment products begin.
Read and normalize market inputs for supported assets.
Turn published market performance into a fantasy-league score.
Buy, sell, custody or transfer an asset merely because a player drafts it.
Use $LEAGUE holdings, cosmetics or profile status to improve market-return scoring.
Invent replacement prices when an accepted scoring source is unavailable.
Treat Stock Tokens as ownership of the underlying shares they reference.
Every production round should be reproducible from its asset identities, accepted source snapshots, normalization rules and scoring specification.
The intended round model is simple enough to understand in seconds and strict enough to become deterministic once public scoring is finalized.
Choose exactly five supported market assets before the round lock.
The round records a defined asset set and pricing boundary.
Market movement is observed during the round window.
Returns are converted into a deterministic league result.
Players are ordered by the final round score.
$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.
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.
Hood League is designed around a mixed market universe rather than a single asset class.
Robinhood-issued Stock Tokens may provide the equity-reference layer where supported and legally available.
Example class: U.S. equity referencesMajor crypto assets can provide continuously moving market inputs and a complementary risk profile.
Example class: BTC · ETH · DOGESelected independent tokens deployed on Robinhood Chain may be included when contract identity and liquidity can be verified.
Contract-first identificationDisplaying an asset does not mean Hood League recommends, sponsors, guarantees, or is affiliated with that asset or issuer.
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.
assetIdsymbolassetTypechainIdcanonicalContractdecimalspriceSourcenormalizationverifiedAtstatusscoringEligiblefailurePolicy{
"assetId": "stock-token:AAPL",
"symbol": "AAPL",
"assetType": "stock-token",
"chainId": 4663,
"canonicalContract": "verified-from-official-registry",
"priceSource": "robinhood",
"normalization": "underlying-mid × currentMultiplier",
"scoringEligible": true
}
Independent Robinhood Chain assets are matched by exact configured contract address. A duplicate ticker or lookalike token must never inherit another asset's identity.
The current website uses a server-side aggregation endpoint. Each market category has a defined source and failure behavior.
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.
| Category | Primary source | Change window | Failure behavior |
|---|---|---|---|
| Stock Tokens | Robinhood Stock Token API | vs previous U.S. regular close | Display fallback may be used; otherwise “—” |
| Major crypto | CoinGecko | 24 hours | “—” when unavailable |
| Selected onchain tokens | DEX Screener | 24 hours | Only exact configured contracts are accepted |
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.
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.
Load canonical Stock Token metadata and the multiplier valid at the snapshot boundary.
Convert raw REST underlying quotes to the token-equivalent value when required.
Record multiplier/corporate-action changes across the round window.
Compare economically equivalent start/end values rather than raw unadjusted numbers.
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.
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.
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.
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.
Record the expected end boundary and freeze the lineup state.
Check source, timestamp, freshness, multiplier and canonical asset identity.
Run the versioned scoring specification against accepted snapshots.
Store the score, scoring-spec version and data provenance needed to reproduce it.
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.
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.
Robinhood's public RPC endpoints are rate-limited and not recommended for production. Robinhood documentation recommends a provider such as Alchemy for production infrastructure.
Hood League connects to EVM-compatible wallets. Users keep custody of their keys and explicitly sign any future onchain transaction.
The landing page discovers MetaMask and compatible injected providers using modern EVM wallet discovery plus a legacy provider fallback.
Hood League should never request a seed phrase, private key, or wallet recovery secret. Connection and signatures happen inside the user's wallet.
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.
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.
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.
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;
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.
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.
Onchain tokens should be resolved from configured contract addresses, not ticker text alone.
If a required feed fails and no approved fallback exists, render an unavailable state instead of fabricated data.
Store source timestamps and the Hood League fetch timestamp so scoring can be audited later.
A UI fallback can keep a market board readable without automatically becoming an accepted scoring source.
$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.
Access to selected seasonal or specialized league formats.
Planned utility for player- or community-created competitions.
Cosmetic and profile features that do not alter market scoring.
Potential product-focused participation around league formats and supported experiences.
$LEAGUE is not described as equity, revenue share, guaranteed yield, guaranteed appreciation, or a promise of financial return.
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.
The fixed supply is minted to the launch curve under a selected launch configuration.
Users buy and sell against the bonding curve. Price changes with curve utilization.
Once the configured sellable allocation is exhausted, graduation can execute automatically.
A Uniswap v4 pool is created and its liquidity position is permanently locked by the protocol.
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.
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.
/api/marketJSON · cached at the edge
{
"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.
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);
}
function displayPrice(asset) {
if (!Number.isFinite(asset?.price)) return '—';
return new Intl.NumberFormat('en-US', {
style: 'currency',
currency: 'USD'
}).format(asset.price);
}
Hood League should not put every UI interaction onchain. Future contracts should be used where public verification, ownership or settlement materially improves the product.
Canonical league configuration and creator/league identifiers where public ownership matters.
Commit or attest finalized round results after the offchain scoring pipeline reaches deterministic output.
Token-aware access, creation or identity functions after the official token exists.
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.
Self-custody. Wallet keys remain with the user. Hood League does not need private keys or seed phrases.
Explicit chain validation. Transaction-enabled features should verify chain ID before requesting a signature.
Contract verification. Official contract addresses must be published from Hood League-owned channels and verified on the relevant explorer.
Data provenance. Market snapshots should record source, timestamp and normalization path.
No fake fallback data. Missing sources should degrade to an unavailable state rather than random prices.
Audit status is explicit. Hood League should never imply smart contracts are audited until an audit has actually been completed and published.
Pre-launch documentation should describe constraints as clearly as capabilities. These limitations are expected to change as production infrastructure is completed.
The website refreshes normalized snapshots on an interval. Provider caching and network latency can make display data differ from an exchange's latest trade.
Sample scores, ranks and leaderboard entries are product demonstrations until the production scoring layer is active.
Connecting a wallet only exposes permitted account/network information. Hood League does not receive the wallet's private key.
$LEAGUE supply/launch parameters shown before deployment are project plans, not verified onchain facts.
Robinhood APIs, crypto data providers, RPC infrastructure, sequencer availability and third-party protocols can become unavailable.
Legal availability, token controls, liquidity or data quality may cause an asset to be unavailable for a future round.
Hood League is a fantasy-market product. It is not a broker, exchange, custodian or financial adviser. Product, market-data and onchain features remain subject to the applicable terms and risk disclosures.
Current Robinhood Chain brand guidelines require the full “Robinhood Chain” name, require “Stock Tokens” terminology, prohibit implying endorsement, and contain restrictions around references to the HOOD/$HOOD ticker in Robinhood Chain-related external content. Product and marketing surfaces should be reviewed against the latest official guidelines before public campaigns.
Programmable wallet infrastructure, commonly ERC-4337, enabling features such as batching, policies and gas sponsorship.
An automated pricing mechanism where token price changes as curve reserves and sold supply change.
The numeric identifier wallets use to distinguish EVM networks. Robinhood Chain mainnet is 4663.
Robinhood Stock Token metadata used to account for corporate-action scaling between raw underlying price and token-equivalent UI value.
The Pons V2 transition from bonding-curve trading to a Uniswap v4 pool after the configured curve sells out its tradable allocation.
The JSON-RPC interface used by wallets and applications to read blockchain state and submit transactions.
A model where the user controls the wallet keys needed to authorize transactions.
A Robinhood-issued ERC-20 tokenised debt security providing economic exposure to a referenced security without underlying share ownership rights.
Added status vocabulary, product boundaries, canonical asset registry, corporate-action normalization, candidate scoring spec v0.1, round finalization and known limitations.
Added Stock Token model, market API, wallet/network architecture, $LEAGUE plan and security sections.
Hood League documentation should treat protocol and network documentation as versioned dependencies. These links are the primary sources used for the current documentation pass.
Documentation reflects the current pre-launch Hood League product and public protocol documentation available at the time of this revision.