Sui Mainnet Two-Day Outage Tests Layer-1 Resilience as Base, Arbitrum, Ondo Make Moves

Sui’s mainnet ground to a halt for two consecutive days in late May, suspending user transactions and rattling confidence in a chain that had been riding a wave of adoption. According to the original report, the outages originated from an interaction conflict between the Address Balances feature and gas billing logic introduced in version 1.72. A temporary fix deployed earlier carried a known issue that could trigger outages with an extremely low probability—a calculated risk that backfired when epoch transition problems piled on, leaving validator nodes running yet unable to process any user transactions.

The incident hits a network that just weeks ago saw institutional staking and a Paga partnership drive an 18% price surge. Now the core team must publish a post-mortem and convince builders, validators, and DeFi protocols that the chain’s upgrade pipeline can handle complexity without collateral damage. The outage pattern—a bug introduced in a protocol upgrade, then a patch with a tiny failure probability that nonetheless materialized—will feel familiar to anyone who tracked Solana’s early outages. For competing layer-1s, the new uptime bar is being drawn not by perfection but by how fast a network can recover and communicate.

Base Slashes Empty Blocks With Azul Multiproof Upgrade

On the scaling front, Base rolled out its Azul mainnet upgrade, combining TEE and zero-knowledge proofs to cut withdrawal confirmation times and push decentralization further. The new client architecture reduced empty block volume by about 99% and has already handled peak loads of 5,000 transactions per second. With total value locked sitting near $4.4 billion at the end of May, Base is tilting the L2 race away from just cheap fee throughput and toward verifiable, low-latency infrastructure that can serve as a credible settlement layer for onchain activity.

That such a sweeping performance jump could be delivered via a multiproof mechanism underscores a broader trend: L2s are increasingly differentiating through protocol-level optimizations rather than just fee subsidies. Users may not notice the cryptographic plumbing, but they will notice fewer failed transactions and faster finality—especially when Base competes directly with alternative L2s and even fast L1s for DeFi volume and developer mindshare.

Arbitrum Foundation Wants $43.5 Million for 2027 Operations

The Arbitrum Foundation requested 16 million in stablecoins, 1,740 ETH, and 230 million $ARB tokens—roughly 3.7% of total supply—from its DAO to cover 2027 operating expenses. The ask lands at a time when the DAO generated about $23.49 million in revenue in 2025, meaning the proposal would allocate a sum nearly double last year’s intake. Governance discussions are now weighing whether the foundation’s technical infrastructure, ecosystem development, and marketing warrant a treasury drain of that size.

Large DAO budget requests are no longer unusual, but they force communities to confront the tension between spending to stay competitive and preserving treasury runway. With $ARB tokens making up such a significant chunk of the total, the vote will likely become a proxy for sentiment on the token’s long-term valuation and the DAO’s cost discipline. If the proposal fails, the foundation may need to trim operations or find alternative revenue streams—both outcomes that could reshape how Arbitrum builds and markets itself in 2027.

Ondo Names New CEO After Founder’s Sudden Death

Ondo Finance announced the unexpected passing of founder Nathan Allman. Ian De Bode, who served as President and oversaw strategy and daily operations for over two years, steps into the CEO role. The RWA-focused protocol had only recently cemented its institutional credibility through a live tokenized Treasury settlement with JPMorgan. Leadership transitions at a time of rapid growth always carry execution risk, but the stability De Bode brings from inside operations may insulate the project from immediate disruption.

Still, Ondo’s tokenization pipeline depends heavily on partnerships and regulatory goodwill—areas where a founder’s personal relationships can be hard to replicate. The market will watch closely for any shift in strategic direction or integration tempo as the new CEO settles in.

Polymarket KYC Fears Clarified; Regulatory Clouds Linger

Reports that Polymarket was mandating trader identity verification turned out to be narrower than described. A company representative clarified that a new beta product requires KYC only for selected testers; the existing platform will not impose new rules. The earlier alarm, however, pointed to genuine gray-zone access via bots and Telegram tools from restricted regions. Polymarket’s careful framing suggests it is testing identity verification as a feature rather than a forced platform-wide shift, perhaps to gauge regulatory comfort without alienating its core user base.

The clarification lands during a period of intense regulatory posturing, including banks lobbying to rewrite landmark crypto legislation days before a Senate vote. For prediction markets that operate at the intersection of financial gambling and information markets, even a limited KYC beta becomes a signal of how platforms might adapt to mounting legal scrutiny without breaking the user experience that makes them popular.

Additional Developments: Aave, Yuga Labs, and Developer Security

Aave Labs proposed a standardized technical asset listing framework that would unify asset review and ongoing monitoring across V3, V4, and Horizon deployments—bringing consistency and transparency to what can sometimes be a chaotic governance process. Separately, Yuga Labs restructured its ApeCoin organization, cutting coordination costs and transitioning ApeChain’s core teams under Yuga Labs as ApeCo lead Cam stepped down. Meanwhile, Socket’s research team exposed a supply chain attack dubbed TrapDoor that spans npm, PyPI, and Crates.io, targeting developers with crypto-stealing payloads disguised as legitimate packages. The attack highlights a persistent weak point in the developer tooling pipeline that chains and protocols can’t easily police, even as they ship upgrades like the ones that tripped up Sui and propelled Base forward.