200k TPS orderbook
What happened
- Social posts describe Reya's orderbook architecture handling up to 200,000 transactions per second. - The specific throughput figure cited is 200k TPS, moving systems from discrete to continuous price formation. - Such throughput reduces stale quotes and changes microstructure dynamics that HFT firms and venues must manage (x.com).
Why it matters
An order book is the live list of bids and offers in a market, and Reya says its architecture can handle as many as 200,000 transactions per second. (blog.reya.network) Reya Labs published that figure on November 16, 2025, in a post announcing a partnership with EigenCloud, saying the system runs a “fully verifiable onchain orderbook” while keeping executed trade data on Ethereum. (blog.reya.network) The company’s docs describe the basic split in plain terms: trade executions go to Ethereum Layer 1, while the much larger stream of order-book updates goes to a separate data-availability layer, with both tied together by zero-knowledge proofs. (docs.reya.xyz) That design addresses the central bottleneck in onchain trading. Reya says order data can be 100 to 1,000 times larger than ordinary transaction data, which is why general-purpose chains have struggled to run exchange-style books directly onchain. (blog.reya.network) In a traditional limit order book, prices update continuously as traders add, cancel, and match orders. Academic microstructure research describes that process as continuous price formation layered on top of a discrete quote grid. (arxiv.org) When a market cannot process updates fast enough, quotes go stale. National Bureau of Economic Research researchers use the same term to describe the race by fast traders to exploit outdated prices across venues, while Bank for International Settlements researchers document similar latency-arbitrage behavior around stale reference prices. (nber.org) (bis.org) Reya’s current public docs show an earlier stage of that roadmap. Its network documentation says the existing chain layer can reach 100 millisecond block times and up to 30,000 transactions per second, with first-in, first-out ordering intended to reduce front-running and harmful maximal extractable value. (docs.reya.xyz) A later architecture post dated October 1, 2025, said ReyaChain would move more trading logic into specialized execution nodes that can give millisecond-level pre-confirmations before final inclusion on Ethereum. That post described the order book as fully onchain and verifiable, with rollout planned in stages. (blog.reya.network) The practical claim behind 200,000 transactions per second is not just raw speed. It is that an onchain venue can absorb enough order updates, cancels, and fills to behave more like an electronic exchange than a slower batch system. (blog.reya.network) (arxiv.org) Reya has not published, in the materials reviewed here, a public benchmark note breaking out exactly how that 200,000 figure was measured under production conditions. What it has published is the architecture: Ethereum for execution data, a separate data layer for order flow, and a claim that this combination is enough to keep an order book live at exchange-like speeds. (blog.reya.network) (docs.reya.xyz)
Key numbers
- Social posts describe Reya's orderbook architecture handling up to 200,000 transactions per second.
- The specific throughput figure cited is 200k TPS, moving systems from discrete to continuous price formation.
- An order book is the live list of bids and offers in a market, and Reya says its architecture can handle as many as 200,000 transactions per second.
- (blog.reya.network) Reya Labs published that figure on November 16, 2025, in a post announcing a partnership with EigenCloud, saying the system runs a “fully verifiable onchain orderbook” while keeping executed trade data on Ethereum.
Quick answers
What happened in 200k TPS orderbook?
Social posts describe Reya's orderbook architecture handling up to 200,000 transactions per second. The specific throughput figure cited is 200k TPS, moving systems from discrete to continuous price formation. Such throughput reduces stale quotes and changes microstructure dynamics that HFT firms and venues must manage (x.com).
Why does 200k TPS orderbook matter?
An order book is the live list of bids and offers in a market, and Reya says its architecture can handle as many as 200,000 transactions per second. (blog.reya.network) Reya Labs published that figure on November 16, 2025, in a post announcing a partnership with EigenCloud, saying the system runs a “fully verifiable onchain orderbook” while keeping executed trade data on Ethereum. (blog.reya.network) The company’s docs describe the basic split in plain terms: trade executions go to Ethereum Layer 1, while the much larger stream of order-book updates goes to a separate data-availability layer, with both tied together by zero-knowledge proofs. (docs.reya.xyz) That design addresses the central bottleneck in onchain trading. Reya says order data can be 100 to 1,000 times larger than ordinary transaction data, which is why general-purpose chains have struggled to run exchange-style books directly onchain. (blog.reya.network) In a traditional limit order book, prices update continuously as traders add, cancel, and match orders. Academic microstructure research describes that process as continuous price formation layered on top of a discrete quote grid. (arxiv.org) When a market cannot process updates fast enough, quotes go stale. National Bureau of Economic Research researchers use the same term to describe the race by fast traders to exploit outdated prices across venues, while Bank for International Settlements researchers document similar latency-arbitrage behavior around stale reference prices. (nber.org) (bis.org) Reya’s current public docs show an earlier stage of that roadmap. Its network documentation says the existing chain layer can reach 100 millisecond block times and up to 30,000 transactions per second, with first-in, first-out ordering intended to reduce front-running and harmful maximal extractable value. (docs.reya.xyz) A later architecture post dated October 1, 2025, said ReyaChain would move more trading logic into specialized execution nodes that can give millisecond-level pre-confirmations before final inclusion on Ethereum. That post described the order book as fully onchain and verifiable, with rollout planned in stages. (blog.reya.network) The practical claim behind 200,000 transactions per second is not just raw speed. It is that an onchain venue can absorb enough order updates, cancels, and fills to behave more like an electronic exchange than a slower batch system. (blog.reya.network) (arxiv.org) Reya has not published, in the materials reviewed here, a public benchmark note breaking out exactly how that 200,000 figure was measured under production conditions. What it has published is the architecture: Ethereum for execution data, a separate data layer for order flow, and a claim that this combination is enough to keep an order book live at exchange-like speeds. (blog.reya.network) (docs.reya.xyz)
