EVM is not slow. We have achieved over 1 million TPS on a single node while still Merkleizing every block.
Introducing FAFO
Fast Ahead-of-Formation Optimization (FAFO) is a scheduler that enables high throughput for chains by reordering transactions before block formation.
▪ Over 1 Million Merkleized EVM-Compatible Transactions/Second
▪ 91% Cheaper Than Sharded Execution
▪ Open Source
To evaluate scalability in an Ethereum-like environment, we benchmark FAFO on native ETH transfers and ERC20 transfers. Transactions are scheduled by FAFO, executed in REVM, with storage and merkleization handled by QMDB.
FAFO achieves near-linear scaling across cores and sustains one million TPS while maintaining state verifiability. FAFO also scales vertically on a single machine. This enables FAFO to achieve more than 1M TPS 91% cheaper than state-of-the-art sharding approaches.
Introducing Quick Merkle Database (QMDB), a high-performance verifiable database optimized for blockchains.
• 2.28M state updates per second, 1M TPS (benchmarked transfers per second).
• Benchmarked with workloads up to 15B (10x Ethereum’s 2024 state) and proven capacity to scale to 280B entries on a single server.
• Single read per state access, O(1) I/O for updates, and in-memory Merkleization on a footprint as small as 2.3 bytes per entry.
• Efficiently scales across both consumer grade and enterprise hardware.
Developed by LayerZero Labs, QMDB is MIT and apache-2 licensed and completely open-source.
QMDB is an SSD-optimized state database with in-memory Merkleization, cutting write amplification and DRAM needs.
It unifies world state and Merkle tree storage, uses an append-only log for state updates, and eliminates disk reads/writes during Merkleization.
QMDB performs state reads with a single SSD read, state updates with O(1) SSD I/O, and performs Merkleization fully in-memory with zero SSD reads or writes.
These operations approach the theoretical optimality regarding disk I/O complexity.
LayerZero V2 overhauls how developers secure their cross-chain messages.
With Decentralized Verifier Networks (DVNs), both V1 and V2 application owners can configure a custom Security Stack based on their specific needs.
Dive into DVNs 🧵
1/ In V2, messages are verified through DVNs selected by application owners.
Any entity – be it a bridge, oracle, attestation service, zkLightClient, enterprise company, DAO, etc. – can permissionlessly create a DVN to verify messages for applications built on LayerZero.
2/ These DVNs create a powerful and configurable Security Stack for applications called “X of Y of N.”
For example, a "1 of 9 of 15" configuration requires consensus from the following DVNs for a message to be verified:
* 9 from a selected pool of 15 DVNs, and
* 1 specific DVN
We formally define the fungible token coloring problem of attributing (coloring) fungible tokens to originating entities (minters), and present, to our knowledge, the first practical onchain algorithm to solve it.