Reza Sabernia, Product - Ethereum & Solana at @coinbase, is joining us at Solana Summit Canada. @Web3WalletMan is shaping how users access Solana at Coinbase, making onchain markets easier to discover and use. Sept 23–24, Toronto, St. Lawrence Market North.

Our Q2 2026 @ethereum validator performance report is live. Some highlights: ➡️ Reliability: 99.97% uptime vs. 99.76% network (0 slashing or double-signing events since inception) ➡️Rewards: 2.87% APY vs. 2.80% network ➡️Scale & distribution: 4.76M ETH staked to Coinbase validators (12.16% of total staked ETH) ➡️Client & relay diversity: 2 consensus clients (Lighthouse 72%, Prysm 28% of our fleet), 3 execution clients (Nethermind 39%, Reth 33%, Geth 28% of our fleet), and 7 MEV relays, with OFAC screening available as an option Read the full report: coinbase.com/blog/ethereum-v…

Ethereum is about to fundamentally change how blocks are executed. With the upcoming Glamsterdam hardfork, it's shipping EIP-7928: Block-level Access Lists, a proposal that brings parallelization to the EVM. Here's a short explainer of what it is, how it works, and why it's a big deal for scaling. Let's start from the top. Alongside EIP-7732 (ePBS), EIP-7928 is the execution-layer (EL) headliner for Glamsterdam. Like ePBS, the main focus has been scaling Ethereum, though both proposals come with a bunch of other, equally important properties on the side e.g. removing trust requirements from the PBS pipeline or improving sync. EIP-7928 adds a Block Access List (BAL) to every Ethereum block. A BAL is a list of accounts and storage slots that the block touches, but that's not all: it also contains post-transaction state diffs (this part is critical!). Post-transaction state diffs tell you what the state looks like after each transaction. Quick example: user A swaps 1 ETH for DAI on DEX B. The BAL tells you that user A's ETH balance decreased by 1 ETH + tx fees and their nonce went up by 1; that DEX B's ETH balance went up by 1 ETH; and that inside the DAI contract, user A's DAI balance increased while DEX B's decreased. In other words, all of that info becomes statically available, something that previously required tracing the transaction. Client software (Geth, Nethermind, Besu, Erigon, Reth, Ethrex, Nimbus) can use this to do a few very powerful things: 1. Parallelize transaction execution. Knowing the post-state of each tx resolves the dependencies between them. No transaction has to wait on the previous one anymore, so execution can be perfectly parallelized. Instead of large parts of block validation sitting idle waiting on sequential execution, clients can finally make much better use of modern hardware. 2. Batch prefetch. One of the most cumbersome jobs for a node has been fetching the state needed for execution from disk. Because state locations (e.g. the exact storage slot in the DAI contract where user A's balance lives) are only discovered along the way, while executing, state-fetching has been a real drag on scaling: it blocks execution, takes time, and eventually slows everything down. With BALs, everything a node needs for execution is known upfront and can be loaded into cache in one go, in parallel. This speeds things up even further. 3. Parallelize post-state root calculation. Another expensive task is walking the updated state tree to compute the post-state root, which is needed so that everyone agrees on what's on disk after executing the block. With the post-tx state already in the BAL, nodes can do this in parallel while executing. A heavy task that used to wait until all transactions had finished can now run alongside prefetching and execution. 4. Snap sync (v2). An often overlooked, less sexy aspect of blockchains is syncing. Nodes need to catch up with the chain, and they need to catch up faster than the chain progresses. Today, most nodes do snap sync: downloading blocks, headers, and state in parallel while chasing the tip, and then "healing" the database once they're close to the head. Healing means asking peers for trie nodes, receiving them, validating them, and updating the local DB. It's iterative, networking-heavy, can take a while, and especially higher throughput pushes that phase to its limits. BALs help here too: with snap v2, nodes can catch up to the tip and skip the healing phase entirely. Syncing at higher throughput becomes more robust and reliable. So, to summarize, a BAL contains two things: -> The state locations the block accesses -> The state changes after each tx (incl. the new values) We're already seeing big performance gains today: on 6-core machines, EL clients validate blocks up to 5x faster, making block gas limits of 300M a very realistic outcome. ePBS will add to that by decoupling the block from the payload, giving validators 2-4x more time for execution. To not overshoot (security stays priority #1), the fork will likely ship with a 200M gas limit, but we shouldn't be stuck there for long before pushing to 300M and beyond. That's a 10x in scaling since we started taking the topic seriously, without touching hardware requirements. None of this would have happened without people going all-in, heads down, shipping: so many hours spent in calls debating the right design, so many iterations refining the specs, and tons of test cases written (and still being worked on). The road from whiteboard to production-ready code has been a journey, and we're not at the finish line yet, but from what I can tell, things look super bullish for Ethereum. Glamsterdam will be a fork that shows what's possible when a distributed, decentralized community works on a shared goal, laser-focused on providing enough block space to onboard the next wave of users.

Our Q2 2026 @Solana validator report is live. Coinbase validators outperformed network averages in Q2: • 6.52% APY vs. 6.38% network average • 0.035% skip rate vs. 0.136% network average • 41.63M SOL staked across 23 validators in 7 countries • Fleet now runs on DoubleZero and is preparing for the Alpenglow upgrade later this year Read the full report: coinbase.com/blog/q2-2026-so…

We’ve upgraded our full @Solana validator fleet to support the network-wide 60M → 100M CU increase. This upgrade unlocks +66% more compute capacity per block for higher transaction throughput. 24 hours post-upgrade: → Vote rate: Steady → Skip rate: Flat → Delinquencies: 0 → RPC availability: 100% Scaling throughput without compromising network reliability.

Coinbase’s @Solana validator is now connected to @DoubleZero Edge. By utilizing high-bandwidth, ultra-low latency infrastructure, we're supporting technology that delivers market data to traders faster and helps upgrade onchain trading infrastructure. Building a faster, more robust onchain future. Onward.

Our Q1 2026 Solana Validator Performance Report is live. Our Solana validators at a glance: - 40.48M SOL staked (9.52% of total staked SOL) across validators distributed across 6 countries and 2 bare metal providers - Delivering a 7.02% APY (vs. network 6.95%) and a skip rate of 0.041% (vs. network 0.198%) - Supporting 5 validator clients (Harmonic, Jito, JitoBAM, Firedancer, and Rakurai) as primary or secondary - Runs on 100% bare metal servers (AMD EPYC 9275F and 9575F)

A quick post on how ePBS changes Ethereum scaling: terencechain.com/writing/epb…

Base + USDC The agentic lineup

Coinbase is proudly participating in Alpenglow community cluster to support @solana and its community.