Source hierarchy
- Official Robinhood Chain technical documentation.
- Robinhood legal terms, product disclosures, newsroom posts, and regulatory filings.
- Official Ethereum and Arbitrum documentation.
- Canonical contracts, verified explorers, and direct onchain observation.
- Official documentation from third-party projects.
- Reputable reporting and independent analysis.
- Social posts only as leads, never as standalone confirmation.
Contract verification
Contract names and symbols are not sufficient. Verification should match the network, full address, official publishing source, proxy implementation, administrator permissions, pause or blacklist controls, and the date checked.
Project verification
Project reviews examine the official domain, documentation, mainnet or testnet status, deployed contracts, custody model, administrative controls, upgradeability, available audits, liquidity where relevant, and recent activity.
How absence of evidence is described
“Not announced” does not mean impossible. “No verified evidence found” does not prove that an event or product cannot exist. “No official incident identified” does not prove that no incident occurred.
Dates and review metadata
datePublished records first publication. dateModified changes only after a material page change. lastVerified changes when the relevant facts are checked again. Build and deployment time must not be used as an editorial date.
Review cadence
| Information | Typical review |
|---|---|
| RPC, chain ID, explorer | Weekly and after official changes |
| Token and airdrop status | Frequently during active speculation |
| Canonical contracts | After official registry updates |
| Architecture | After upgrades or material documentation changes |
| Ecosystem projects | Regular status review |
| Security alerts | As events develop |
| Regulation | After verified legislative or regulatory developments |
Conflicting sources
When reliable sources conflict, Hoodchain.info identifies the disagreement, prioritizes the source closest to the underlying fact, preserves jurisdiction and date context, and avoids presenting the disputed interpretation as settled.
Structured resources
Public files such as facts.json , entities.json , sources.json , and llms.txt provide concise versions of information already explained for people on the site. They do not replace the visible pages or primary sources.