THE VERA PROTOCOL
Open Infrastructure.
Verifiable State.
Final Blocks.
Vera Protocol is an open-source Layer-1 blockchain written in Rust: Tendermint BFT consensus with final blocks, a Merkle-committed state you can verify through proofs, and an Ethereum-compatible virtual machine. The public testnet is live.
Fast Finality
Median 0.55 s from submission to a final block on the public testnet.
Verified Security
Every validator re-executes each block and checks its state root before voting.
Open Source
Apache-2.0 code on GitHub, with GPG-signed releases and published checksums.
Sustainable
Proof of Stake: no mining, and a node runs on a small server.
TECHNOLOGY
How VERA
Works
Four parts, all in the open-source node: a consensus protocol from the research literature, an authenticated state, a standard virtual machine, and releases anyone can check.
Explore Technology
Tendermint BFT
Validators holding 2/3 of the stake sign every block, so a committed block is final, with no reorgs.
Authenticated State
A BLAKE3 sparse Merkle tree commits to every account; proofs are served over RPC.
EVM
Solidity contracts run on revm (Cancun rules) and work with MetaMask, Hardhat and ethers.
Verifiable Releases
Every node release is signed and checksummed; a node reports the hash of the binary it runs.
MEASURED PERFORMANCE
Engineered for Real-Time Execution.
Measured, Not Promised.
Every number below was measured on VERA node v0.2.8.1 or v0.2.9.1: on the public testnet, or in benchmarks anyone can reproduce. Blocks are decided by Tendermint BFT consensus: once a block is committed it is final, with no forks and no probabilistic confirmations.
Time to finality
20 transfers sent to the public testnet, one at a time. Each dot is one transfer, from submission to a final block.
Throughput under sustained load
Transfers sent for 30 s at a fixed rate to the public testnet, counted when final. Three runs at each rate, every transfer included. At 3,500/s latency kept growing: the network was saturated.
v0.2.9.1 against v0.2.8.1
Execution rules v2 (fee credits once per block, one state commitment per block) and a lighter mempool admission. Measured on one CPU core. Each metric on its own scale.
Show the data
| Test | v0.2.7 | v0.2.8.1 | v0.2.9.1 |
|---|---|---|---|
| Sustained load, public testnet, 30 s at 2,500 transfers/s | – | – | 2,445 / 2,440 / 2,433 TPS (median 2,440), all included |
| Sustained load, public testnet, 30 s at 3,000 transfers/s | – | – | 2,861 / 2,913 / 2,886 TPS (median 2,886), all included |
| Sustained load, public testnet, 30 s at 3,500 transfers/s | – | – | saturated: latency kept growing |
| Submission to final block under sustained load (median) | – | – | 0.74 to 0.98 s |
| Time to finality, public testnet (20 transfers, idle network) | median 584 ms | median 554 ms, min 172 ms, max 868 ms | – |
| Throughput, public testnet: batches of 800 / 1,600 / 3,200 / 6,400 / 12,800 transfers | 231 / 471 / 640–683 / ~700 TPS; 12,800 rejected (5,000 pending max) | 274 / 466 / 629 / 916 / 895–1,030 TPS (median 984) | – |
| Execute a block of 2,550 transfers, one CPU core (lab) | – | ~420 ms | ~60 ms |
| Mempool admission per transaction, one CPU core | – | ~260 µs | 110–160 µs |
| Node start-up, copy of a validator's data (497 blocks) | 30.8 s | 0.25 s | – |
| Proposal of a 3,000-transfer block, sent between validators | ~3.2 MB | ~0.2 MB | – |
| Apply a block of 1,500 transfers, 100,000 accounts (lab) | 46 ms | 46 ms | – |
| Fault tests (crashes, pauses, mixed versions) | 0 forks | 0 forks, 100% of transactions included | 0 forks, 100% of transactions included |
Sustained load: measured on October 25, 2026 with VERA node v0.2.9.1-testnet. Signed plain transfers sent for 30 s at a fixed rate, half of them through the public RPC endpoint, to the public testnet (2 active validators in different data centers, one on a 1-vCPU VPS); a run counts from its first submission to the last block carrying its transfers, and inclusion is checked on chain. Median of three runs. Time to finality, batch throughput and the v0.2.7 column: measured on October 21, 2026 with v0.2.8.1-testnet and v0.2.7. Block execution and admission: one node on one CPU core, state root included (lab benchmark). Fault tests with crashes, pauses and mixed versions: 0 forks.
WHAT VERA STANDS FOR
Verifiable Execution & Runtime Architecture.
From the Latin vera, "true". Every block is re-executed and checked by every validator before it is final: nothing is accepted on trust. Below, what runs on the public testnet today and what comes next, kept apart on purpose.
- Tendermint BFT consensusBlocks are final on commit, with no reorgs: validators holding at least 2/3 of the stake sign every block.
- Verifiable executionEvery validator re-executes each proposed block and checks its state, transaction and receipt roots before it votes.
- Cryptographic stateA sparse Merkle tree commits to every account; a fixed test pins its root so it can never change silently between versions.
- Deterministic runtimeValidators on different versions reach the same state root in fault tests; native Flat-DAG programs are checked before they enter the mempool.
- Compact block propagationLarge proposals carry transaction hashes instead of transactions; validators rebuild them from their own mempool.
- One state commitment per blockReceipts carry no per-transaction state root and fee credits are applied once per block, so the state tree is hashed once per block.
- Asynchronous executionAgree on the order of a block first, and execute it while the next one is being agreed; its state root follows a block or two later.
- Parallel executionTransactions that touch different accounts run at the same time, on as many cores as the machine offers.
- Light-client verifierCheck blocks and balances yourself, from a phone, without trusting any server.
Each step is documented in the public release notes: v0.2.6 (Tendermint), v0.2.8 (compact propagation, throughput), v0.2.8.1 and v0.2.9.1 (execution rules v2).
VERA ECOSYSTEM
What You Can
Build
VERA runs standard EVM contracts, so the tools you already use work on the testnet today. The first applications are in development.
Explore EcosystemDeFi
Swaps and lending as Solidity contracts, final in about half a second.
NFTs
ERC-721 collections that work with standard EVM wallets.
Games
Game state and items as Solidity contracts, deployed with standard EVM tools.
Infrastructure
Indexers, wallets and tools built on the standard Ethereum JSON-RPC.
Tokens
ERC-20 tokens deployed with Hardhat or any EVM toolchain.
Payments
Native VERA transfers from MetaMask or any EVM wallet, at 21,000 gas (0.000021 VERA) each.
FOR DEVELOPERS
Build on VERA
Connect a wallet, get test VERA from the faucet and deploy a contract with the tools you already know.
Try VERA on the
public testnet.
Add the network to your wallet, get test VERA and send your first transaction.