ORCL
Oracle • Robinhood Token
Price
Pools
All 3 indexed pools hold dust liquidity (<$1).
README
ORCL tracks Oracle — BeaconProxy (ERC-20, 18 decimals) on the shared Stock implementation.
Priced by the Chainlink feed “Robinhood ORCL / USD”. Read latestRoundData() from the proxy; staleness is the guard, not the L2 sequencer feed.
Read the price
// Read ORCL correctly on Robinhood Chain (chain 4663). ethers v6.import { ethers } from "ethers";
const provider = new ethers.JsonRpcProvider(RPC);
const feed = new ethers.Contract(
"0x0e6a64a2B58A6693a531E6c555f3A5d042eEA844",
["function latestRoundData() view returns (uint80,int256,uint256,uint256,uint80)",
"function decimals() view returns (uint8)"],
provider
);
// price = stock × uiMultiplier already — do NOT multiply again
const dec = await feed.decimals();
const rd = await feed.latestRoundData();
const priceUSD = Number(ethers.formatUnits(rd.answer, dec));
// the real guard: 24h heartbeat (feeds are 24/5)
const now = (await provider.getBlock("latest")).timestamp;
const stale = Number(now) - Number(rd.updatedAt) > 86400;
// NOTE: do NOT gate on the L2 sequencer feed — it's hardwired to 'down' here.Or just fetch the record
No RPC, no ABIs, no guard logic — gitstock already resolved and guarded everything.
// No RPC or ABIs needed — fetch the whole resolved record.
const r = await fetch("https://gitstock.io/ORCL/stock.json");
const s = await r.json();
s.price.usd // live price (already stock × multiplier)
s.holders // holder count
s.tvlUsd // pool TVL in USD
s.dependents // tokens paired against ORCL
s.feed.proxy // the Chainlink proxy gitstock reads
s.fieldNotes // the quirks that break integrationsField notes — what the docs don't tell you
ORCL's multiplier has already drifted
uiMultiplier() reads 1.002211 — the feed price sits about 0.22% above the headline quote. That's total-return tracking (dividends/yield reinvested through the multiplier), not a feed error.
ORCL has a primary and a secondary feed proxy
Chainlink registers two proxies for this feed, both resolving to the same aggregator with identical data. gitstock publishes Chainlink's canonical primary (proxyAddress) as feedProxy and keeps the secondary under feedProxyAlt. Either reads correctly — use the primary.
The price feed is not on the token
The Stock token carries no price and no feed pointer on-chain — no latestRoundData(), no priceFeed(). The Chainlink feed is a separate, unlinked contract, and the token→feed mapping isn't published anywhere. gitstock resolves it for you (verified via the token factory's own creation events, not by symbol).
⚠ The L2 sequencer gate is hardwired to “down”
Robinhood ships a custom SequencerGate whose source() is currently the zero address — so latestRoundData() returns answer = 1 (down) forever, while the price feeds are healthy. Copy the standard Chainlink pattern require(sequencerUp == 0) and your app will never render a price here. Read the gate for transparency, but don't hard-gate on it yet.
Staleness is the real guard — heartbeat is 24h
Because the sequencer gate is unusable, freshness on the feed itself is the actual safety check. The official heartbeat is 86400s: feeds publish at least daily and more often on deviation (~17min–1h in US market hours, hours apart overnight; 24/5). Only treat a price as stale once now − updatedAt > 86400 — anything tighter false-flags overnight and weekend reads.
Feed price is the TOKEN price, not the stock price
latestRoundData() already returns stock_price × uiMultiplier() — don't apply the multiplier again. Dividends reinvest through the multiplier, so the token tracks total return and drifts above the headline stock price over time. That's why the number here won't match Google Finance.
oraclePaused() is advisory, not enforced
During corporate actions the token oracle is paused. oraclePaused() == true means “price temporarily unavailable”, not zero/error — and it isn't enforced on-chain, so a paused oracle can still return a value. Treat it as a display state; rely on staleness for protection.
Read decimals() on-chain; don't hardcode
Feed answers use the feed's own decimals (8 for these USD feeds). Read decimals() from the proxy every time rather than assuming.
Community notes
No community notes yet — be the first.