
Espresso ☕️ · 2026-11-19 17:41 UTC
Espresso’s 1 Million TPS Is No Longer Theoretical Last month we said Espresso could finalize up to one million transactions per second. The number came from measured throughput of 181 MB/s divided by a 180 bytes, the average size of an ERC-20 transfer. The math was sound. But no one had actually watched the protocol finalize a million transactions per second without slowing down. Now we have. We spun up 87 independent chains, each with its own sequencer and execution client, and had them all flood Espresso with ERC-20 transfers at the same time. As you can see in the video below, Espresso finalized more than one million transactions per second while keeping average finality under one second. The 1M TPS claim is no longer theoretical. For institutions evaluating onchain infrastructure, this is the result that matters. A collateral engine, payments platform, and treasury desk can each run as their own application with their own rules, and every counterparty can treat a transaction as final the moment Espresso confirms it, even at peak volume. Here’s a video with Espresso Systems CTO Jeb Bearer explaining what his team built while showing one of the demo's runs, followed by the full methodology and numbers. The results 1,000,000+ — transactions per second, sustained across 87 chains <0.5 seconds — Espresso finality (same as Espresso's block time), holding steady from ramp-up through peak load ~168 MB/s — data finalized by Espresso every second (didn't even need the full 181 MB/s) As the load generators ramped up, the transaction count climbed past a million per second and stayed there. Finality held in the same narrow band the whole time, at roughly a half a second, so adding load didn't add wait time. What we ran Our engineers stood up 87 independent chains, each built with the Espresso Stack, a lean framework we developed that derives a chain's state directly from Espresso consensus so the chain inherits Espresso's security and performance. We first used the Espresso Stack in the crosschain collateral management demo we built with AWS and introduced onstage at the Digital Asset Summit in March. We used the Besu execution client and gave each chain its own sequencer and a dedicated load generator firing upwards of 12,000 ERC-20 token transfers at Espresso per second. Espresso's job was to finalize the order of transactions and the data behind them as fast as possible without getting bogged down. The tests ran on a 100-node Espresso devnet built to mirror mainnet. While all nodes sat in one AWS region, we purposefully slowed down the messages passing between them to simulate real round-trip times between Europe, Southeast Asia, the US East Coast, Australia and South America, so consensus faced the same delays that Espresso mainnet’s globally distributed validator set would. To ensure this wasn’t a one-off result, we ran the tests dozens of times, including a 10-minute run. The result was always the same. Espresso consistently finalized more than 1 million transactions per second while maintaining subsecond latency. The full setup is in the methodology section below. Proof the data was really there Counting the number of transactions Espresso validators can finalize every second only matters if the data behind those transactions can be used to verify the correct state of an Espresso-integrated chain. To that end, we stood up a full node for one of the Besu chains, which we called a follower node, that had no connection to that chain's sequencer and rebuilt the chain's entire state using nothing but what Espresso finalized. Throughout the run, the follower stayed just a few blocks behind the sequencer. If Espresso had fallen behind or dropped data under load, that gap would have widened, but it never did. Any third party reading from Espresso, whether another chain, a bridge, an exchange or even an auditor, could have tracked that chain's state in real time while the network was handling more than a million transactions per second. Why Espresso can do this Espresso was designed from day one to focus on consensus and finalizing transactions from independent chains as fast as possible, while leaving execution to those chains. Each Espresso-integrated chain orders and executes its own transactions through its own sequencer, and Espresso confirms that ordering, finalizes it and guarantees the data is available, which means total throughput grows as more chains connect while finality stays fast. That stripped-down design is what made two years of steady performance gains possible. The Espresso Stack is the native way to build chains for this design. Earlier integrations with chains running Arbitrum Nitro or the OP Stack needed workarounds, because those frameworks were built around a different model, whereas the Espresso Stack was written for Espresso from the start. Espresso Stack chains carry only what its job requires, with no general-purpose virtual machine, gas token or permissionless contract deployment to pay for, and crosschain tooling comes built in so any outside party can read a chain's finalized state immediately. What this means for institutions The financial system of the future will generate far more transactions than blockchains handle today, and each one will get heavier. AI agents that buy, sell and rebalance on their own and at a pace impossible for humans will skyrocket transaction volume, while post-quantum signatures, compliance data and privacy proofs will add bytes to every transaction. That pressure lands on the property finance cares about most. A trade, a payment or a collateral call is only useful once it's final, and a network that slows down under load forces every counterparty to wait. For a bank, an asset manager or a market infrastructure provider, the benchmark shows that finality can hold steady while volume and transaction size both climb. Institutions also don't have to give anything up to get there. Each application can run as its own dedicated chain with its own rules, fees and permissions, without sharing an execution environment with anyone else. A settlement network that finalizes more than a million transfers per second leaves room for peak-day volume and for the heavier transactions ahead, and because finality arrives in under half a second, counterparties, custodians and other chains can trust a transaction the moment it's final. Get in touch Whether you're exploring institutional blockchain infrastructure or want to go deeper on the demo, we'd like to hear from you. Email us at [email protected]. If you’re a team that already runs a private, permissioned Besu network and are interested in exploring a move to an Espresso-based application environment, check out our docs. Methodology Devnet The Espresso devnet used in the demo ran as a 100-node network, with a handful of larger query nodes serving data and the rest running as lightweight nodes. Simulated round-trip latency (ms) To mirror Espresso mainnet's globally distributed validator set, we added latency to simulate real-world delays. Every packet between two simulated regions carried the measured average round-trip time between those AWS regions. Packets within a region got no added delay, so real in-region latency applied. Chains and load We stood up 87 chains, each with its own execution client, sequencer and load generator sending transactions to Espresso. This article was originally published on the Espresso Systems' blog.
Loading the story on Tree News…