Arbitrum claims 40k TPS, $415K buildathon

Arbitrum is making a pretty direct bet on what wins the next phase of crypto infrastructure. Not memes. Not vague “ecosystem growth.” Actual developer programs tied to money, mentorship, and a cleaner performance pitch. The immediate news is Open House London, which starts May 25 and runs through June 14, with a three-week buildathon feeding into a later in-person Founder House. The backdrop is Arbitrum’s broader push to sell itself as finance-grade blockchain infrastructure, not just a busy Ethereum layer 2. ### What actually launched? Open House London is the next stop in Arbitrum’s 2026 builder program. The format is simple: online buildathon first, then a three-day Founder House later, with workshops, mentorship, live pitches, and access to teams from the Arbitrum Foundation, Offchain Labs, and ecosystem partners. Arbitrum’s own site frames Open House as a pipeline from learning to launching, not a one-off hackathon. (openhouse.arbitrum.io) ### Why is the $415K number real? Because Arbitrum Foundation published the breakdown. The London program has $415,000 in prizes and grants across both the buildathon and Founder House. The buildathon side includes $70,000 for the main open category, $15,000 for AI agent teams, and $30,000 in grants. The Founder House side adds $120,000 for the open category, $60,000 for a Robinhood Chain founder-in-residence track, $30,000 for a Robinhood innovation award, and $20,000 for another AI category. (blog.arbitrum.foundation) ### Where does Robinhood fit in? More than as a logo sponsor. Arbitrum says the Arbitrum Foundation and Robinhood Chain are jointly sponsoring the London prizes and grants, and at least some winner slots are reserved for projects building on Robinhood Chain. That matters because Robinhood Chain’s testnet already launched on Arbitrum earlier this year, with Robinhood committing $1 million to the broader 2026 Open House program. So this buildathon is also a funnel for that chain’s early app layer. (blog.arbitrum.foundation) ### What about the 40,000 TPS claim? That’s the part to treat carefully. I could verify Arbitrum’s current official 2026 performance messaging, and it does not center on a blanket 40,000 TPS claim for the main platform. What Arbitrum is publicly emphasizing right now is response times as low as 100 milliseconds, throughput of up to 6,000 TPS for dedicated environments, and a 98% reduction in transaction cost spikes from its latest pricing model. So the bigger credible story is tunable performance on custom Arbitrum chains — not a simple “Arbitrum does 40,000 TPS” headline. (blog.arbitrum.foundation) ### Why does that distinction matter? Because “TPS” in crypto is often marketing mush. A custom chain with narrow assumptions can hit a very different number than a shared public network handling messy real usage. Arbitrum’s docs and blog are basically saying the useful product is configurability — gas targets, dynamic pricing, faster block times, and dedicated environments that can be tuned for a specific app or business. That is a much more enterprise-friendly pitch than raw peak throughput alone. (blog.arbitrum.io) ### Why keep talking about finance and RWAs? Because that’s where Arbitrum wants to be taken seriously. Its homepage now describes the platform as “finance-native” infrastructure for applications, tokenization, and dedicated blockchain environments. Recent posts lean into predictable fees, performance under load, and enterprise chain design. Basically, Arbitrum is trying to move the conversation from retail crypto activity to stablecoins, tokenized assets, and regulated financial workflows. (blog.arbitrum.io) ### So what’s the real takeaway? The buildathon is the visible part. The real move is underneath it. Arbitrum is packaging capital, custom-chain tooling, and institutional-friendly performance claims into one builder funnel. If that works, the win is not just more apps on Arbitrum One — it’s more teams choosing Arbitrum as the rails for purpose-built chains and onchain financial products. (blog.arbitrum.foundation) (arbitrum.io)