Chain-level risk
Whole chain, not filteredRobinhood Chain as a rollup, from L2BEAT and the findings memo.
- Open risk
- Partial
- Mitigated
- Open riskL2BEAT stage
Rated below Stage 0. The rollup does not yet meet the minimum decentralisation requirements.
L2BEAT - Open riskFraud-proof challengers
Only 2 whitelisted challengers can dispute state roots. Anyone outside that list cannot.
L2BEAT - Open risk
- Open risk
- PartialSequencer
Centralised Robinhood sequencer with a transaction filter that can fail forced L1 transactions. Used after the Vlad Tenev account hack to freeze a related wallet.
Decrypt, Jul 23 2026 - PartialLiveness record
On Sep 4 2026, about 40 minutes of app disruption and a 14-minute gap in batches reaching Ethereum. On Oct 29 2026, a 54-minute gap in state updates. Blocks kept being produced.
CryptoSlate, L2BEAT - PartialStock-token pricing
No confirmed pricing or weekend-gap liquidation incident so far. QuillAudits flags that oraclePaused() is advisory only.
Findings memo - MitigatedRollup stack
Built on the Arbitrum (Nitro) stack, which has a long production track record on Arbitrum One.
Arbitrum blog - MitigatedMonitoring coverage
Blockscout, Etherscan, Arkham and L2BEAT all index the chain, so outages and anomalies are recorded publicly.
L2BEAT
Red flags by type
104 of 106 researched projects in this selection list at least one flag; the most common is no published audit found (103).
Flags by sector
Launchpads has the most researched projects (33); 2 researched projects across all sectors were checked with nothing found.
- At least one flag
- Checked, nothing found
Incidents (10)
Whole chain, not filteredDated incidents from the events file, worded as the sources report them. Sort any column; every row links to its source where one exists.
| What happened | ||||
|---|---|---|---|---|
| Oct 29, 2026 | 54-minute gap in state updates Robinhood Chain | Recorded by L2BEAT | undisclosed | web.archive.org |
| Sep 27, 2026 | Analyst links $18.43M to one rug-pull ring Pons | Mostly Pons V2 launches; decoy contracts and anti-snipe exemptions; largest CRUMBS, LEGS, PINK | $18.4M Extracted across 53 launches (Jul 10 to Sep 21) | theblock.co |
| Sep 4, 2026 | Network disruption and 14-minute batch gap to Ethereum Robinhood Chain, Arbitrum | About 40 minutes of reduced app traffic with delayed oracles and smart-wallet failures | undisclosed | cryptoslate.com |
| Jul 23, 2026 | Vlad Tenev X account hacked to promote fake VLAD token | Robinhood later used the chain transaction filter on the related wallet | $1.3M Approx. extracted (650 ETH) | decrypt.co |
| Jul 15, 2026 | Vlad.fun shuts down over internal integrity issue Vlad.fun | Launchpad offline and consulting legal counsel | undisclosed | cointelegraph.com |
| Jul 12, 2026 | Hacked SpaceX and Starlink X accounts shill a memecoin that rugs | Creators pulled liquidity after a brief run to about $2M market cap | $2.0M Peak market cap | www.kucoin.com |
| Jul 11, 2026 | NOXA Fun pauses then goes offline NOXA Fun | Paused Jul 11, offline Jul 13, lost domain Jul 17; team share about $2.8M; possible soft rug unresolved | $12.0M Fees collected before shutdown | research.4pillars.io |
| Jul 10, 2026 | User-reported scam losses letscash.fun (formerly cashcat.fun) | Self-reported, unverified; includes a $56K CASHCAT holder and smaller $600, $350 and $50 losses | $56.0K Largest single reported loss | protos.com |
| Jul 9, 2026 | Relay warns of self-removing honeypot tokens Relay | Scam tokens use hidden storage to disappear from wallets after purchase; not a Relay breach | undisclosed | news.bitcoin.com |
| Jul 2, 2026 | Fake RIALTO honeypot token impersonates Rialto Rialto | First documented impersonation honeypot on the chain | undisclosed | ourcryptotalk.com |
How to read this
Flags are keyword matches on the researcher's notes for the 106 researched projects in this selection. They count what the sources say; they do not rate a project, and a flag is not a finding of wrongdoing.
Not researched means security was never checked for that project. Checked, nothing found means the research pass found no audit, incident or flag in the sources it looked at; it does not mean the project is unaudited or safe.
Incidents are listed as reported, including events caused by third parties such as impersonation tokens. Nothing here is a judgement of intent.