Verify the sleeve.
Not just the ticker.
Enter a ticker or contract address. Bellside reads supply and proxy wiring directly from chain 4663, states what the chain cannot prove, and lets you freeze the exact reading into a report for a counterparty.
A ticker is a label. The contract is the instrument.
Public chain data proves contract state, token supply, transfers and beacon wiring. It does not prove custody, transfer-agent parity, redemption rights or legal ownership. Bellside keeps that boundary visible.
What is actually on-chain
Nineteen server-pinned Robinhood Token sleeves. Supply is re-read from
totalSupply(); the contract, block and source travel with the number.
| sleeve | class | contract | on-chain supply | transfers | signals | reading |
|---|
Sleeve dossier
Contract state on the left; the derivation and its evidence boundary on the right. Freeze this reading when another party needs to see the same numbers later.
Frozen report
The block, raw supply, evidence and classifier below are immutable. The conclusion is re-derived when displayed; it is never stored as a verdict.
Chain fact, inference, boundary
Bellside separates those three. It will not turn a successful RPC call into a custody claim.
Supply at a named block
totalSupply(), contract address, decimals, chain ID and source RPC are
captured together. The raw uint256 is retained in every report.
One implementation path
All 19 tracked sleeves are 283-byte beacon proxies wired through the same beacon. One implementation change can affect every sleeve.
On-chain does not mean backed
The ledger cannot prove shares held by a custodian, transfer-agent reconciliation, redemption rights or legal ownership. External-only evidence stays unverified.
The weakest signal binds
Signal score is min(), never an average. Badges are derived from raw
evidence on every display and never written into backend storage.
FAQ
What Bellside does, and the line it refuses to cross.
What do I use Bellside for?
Check a ticker or contract before buying it, accepting it, or sending it to a counterparty. Bellside identifies the tracked contract, reads its current supply and exposes the shared upgrade path.
What makes a report immutable?
Each symbol gets one private backend object per UTC hour. It is created with overwrite disabled, content-hashed, and served through its stable Bellside permalink.
Why does a real contract still read unverified?
A contract and its supply are chain facts. They do not prove off-chain custody or redemption. With external chain evidence only, Bellside refuses to produce a final positive custody verdict.
Is Bellside affiliated with Robinhood?
No. Bellside is independent and unaffiliated. Robinhood Chain is named because that is chain ID 4663, where the tracked contracts were measured.