Key Highlights:
- European trading venue 21X and LayerZero reported that a private, permissioned deployment of Zero processed 10,000 order matches per second during a month-long technical pilot.
- The trial tested a fully onchain central limit order book focusing on US equity tokens, achieving a reported 45-fold performance improvement over an EVM layer-two baseline.
- While the milestone marks a notable technical step for institutional onchain execution, sustained operations will require independent testing, regulatory approvals, and real-world market stress testing.
European trading venue 21X and cross-chain infrastructure protocol LayerZero revealed that a private, permissioned implementation of Zero achieved an execution throughput of 10,000 order matches per second during a month-long technical trial. Disclosed on November 4, the test demonstrated an estimated 45-fold performance increase compared to the referenced Ethereum Virtual Machine (EVM) layer-two baseline used for comparison. The figures present a rare, concrete performance metric within an institutional blockchain market that frequently trades on speculative throughput assertions, though private pilot metrics remain distinct from sustained trading under genuine market stress.
Inside the Technical Pilot: Scope and Infrastructure
The pilot between 21X and LayerZero was designed to evaluate a fully onchain central limit order book (CLOB), specifically targeting the exchange mechanics required for US equity tokens. Executing an order book entirely onchain presents substantial engineering hurdles compared to hybrid trading models, where trades are evaluated offchain by conventional matching engines and merely posted to a distributed ledger post-factum. By processing both matching and execution onchain, the test addressed core throughput and latency constraints that have long hindered decentralized and distributed market designs.
Crucially, the trial relied on a permissioned, private instance rather than a public, open network. Operating within a closed architecture allows operators to maintain strict oversight of network membership, data visibility, and hardware specifications. Because validator sets, transactional patterns, and hardware configurations are strictly controlled in private deployments, comparing these findings directly to decentralized public networks requires caution, as public environments face different congestion, network latency, and adversarial conditions.
Addressing Institutional Requirements and Governance Trade-offs
Regulated exchanges require extensive compliance capabilities, including real-time trade surveillance, strict access controls, auditable operational records, and clear protocols for resolving trade breaks or errors. Many institutional participants face regulatory and commercial constraints that prevent them from broadcasting proprietary trading activity across transparent public ledgers. A controlled, permissioned deployment gives institutions the operational predictability and privacy they need while preserving the transparency and programmability of a shared distributed state.
However, running market architecture on a permissioned network introduces trade-offs in governance and trust structures. Operating a private ledger requires specific entities to establish validator rules, authorize participants, manage software updates, and govern emergency failover procedures during outages. While achieving 10,000 matches per second demonstrates processing capacity, it leaves key institutional governance questions to be validated in practice.
Evaluating the 45x Performance Metric and Onchain Dynamics
The reported 45-fold increase in efficiency must be evaluated relative to the specific EVM layer-two baseline selected by LayerZero and 21X. While demonstrating strong execution under the pilot’s defined conditions, the metric may not translate uniformly across all decentralized networks or varied transaction types. In active exchange environments, high cancel-to-fill ratios, rapid order modifications, and intensive pre-trade compliance checks can significantly impact net throughput.
Beyond headline matching counts, venue reliability depends on deterministic latency, rapid finality, robust settlement mechanics, and outage recovery. An exchange operator must also prove that order fairness, market data feeds, and price-time priority rules remain uncompromised during peak activity spikes.
Why This Matters: Tokenization Meets Core Exchange Engineering
Institutional interest in tokenized assets has largely focused on the custody, issuance, and legal structuring of real-world assets (RWAs). However, the operational hurdles of institutional adoption rest equally on secondary market microstructure, including market making, low-latency matching, and orderly trade handling during periods of extreme volatility.
The collaboration between 21X and LayerZero highlights a deliberate push by exchange infrastructure providers to address back-end performance limits directly on distributed ledgers. For 21X and LayerZero, progressing beyond pilot benchmarks will require releasing technical methodologies, undergoing third-party verification, integrating multiple independent institutional participants, and obtaining necessary regulatory clearances. Live volume and operational continuity during volatile conditions will serve as the true measure of whether onchain matching engines can support regulated financial venues.
Frequently Asked Questions
What did the 21X and LayerZero pilot achieve?
In a month-long technical trial disclosed on November 4, a private, permissioned implementation of LayerZero’s Zero handled 10,000 order matches per second for an onchain central limit order book, demonstrating a 45-fold performance gain over a baseline EVM layer-two configuration.
What types of assets were targeted during the test?
The trial focused specifically on the trading and matching requirements of US equity tokens within a fully onchain order book framework.
How does a private, permissioned network differ from a public blockchain in this context?
A private, permissioned network restricts who can validate transactions and view trade data, allowing controlled hardware standards and privacy for regulated institutions. Because public blockchains operate without centralized access controls and face variable hardware and network congestion, performance figures from private trials cannot be directly applied to open public environments.




