Discover
About EBLA Roadmap Technology Security
Economics
Tokenomics Airdrop Staking
Build
Validators Developers
Network
Community FAQ Join Now
⚡ Technology

Why EBLA is
Fundamentally Different

EBLA is not just another blockchain. It uses a Directed Acyclic Graph of blocks (blockDAG) — a fundamentally different architecture that allows parallel processing, faster finality, and higher throughput without sacrificing security.

📐 Architecture

Blockchain vs BlockDAG

Traditional Blockchain

One block at a time

A traditional blockchain adds blocks in a single chain, one after another. If two miners or validators create a block at the same time, only one wins — the other is discarded. This wastes work and creates a hard throughput ceiling. No matter how many validators you have, the chain can only process one block at a time.

EBLA BlockDAG

Many blocks in parallel

EBLA's blockDAG allows many blocks to be created simultaneously and included in the ledger. Instead of discarding competing blocks, the network keeps them all and uses PBFT consensus to establish a final, agreed ordering. The result: over 5,000 transactions per second, with no wasted work and no single bottleneck.

EBLA BlockDAG flow diagram A Genesis block branches into three parallel blocks, which branch into two more, all flowing into a single PBFT-finalized block. G B1 B2 B3 B4 B5 PBFT FINAL Genesis Parallel blocks Finalized

Multiple blocks created in parallel → PBFT consensus finalizes them all into an ordered, irreversible ledger

⏱️ Finality

True Finality in <3.7 Seconds

"True finality" means a transaction is irreversible — not just unlikely to be undone. Here's how EBLA compares:

Bitcoin
~60 min
Probabilistic
You wait for 6 confirmations (~1 hour). Even then, reversal is theoretically possible — just very expensive.
Ethereum
~12 min
Probabilistic
Fast blocks, but "economic finality" via Casper takes ~12 minutes. Reorganizations are still theoretically possible.
EBLA
<3.7s
True Finality
PBFT consensus makes blocks irreversible in under 3.7 seconds. Zero reorganization risk. Permanent from the moment it finalizes.
🔧 Stack

Under the Hood

🔗

BlockDAG

Directed Acyclic Graph allowing parallel block production. Multiple validators propose blocks simultaneously without conflicts.

🗳️

PBFT Consensus

Practical Byzantine Fault Tolerance with VRF sortition. 15 of 24 committee members must agree. Asynchronous, lightweight, and fast.

⛓️

100% EVM

Full Ethereum Virtual Machine compatibility. Every Solidity contract, ethers.js call, or MetaMask wallet works without modification.

🛡️

aBFT Security

Asynchronous Byzantine Fault Tolerant. The network remains secure and live even when nodes act maliciously or go offline.

💾

LZ4 Compression

Database storage compressed with LZ4. Reduces node disk usage by 40–50% compared to uncompressed storage.

🐹

C++ + Go

Consensus and networking in C++. DPoS staking contracts in Go (compiled to EVM). Battle-tested Taraxa codebase foundation.

🔄 EBLA Changes

What's Different from Taraxa

ParameterOriginal TaraxaEBLAWhy it changed
Consensus quorum2/3 (~66.7%)15/24 (62.5%)Custom-tuned threshold for fast finality on a BlockDAG
Inactivity penaltyNone−5% per 10h offlineKeeps validators accountable automatically
Min commissionNone10% enforcedPrevents race-to-zero for validators
Max stake per validatorNone1,000,000 EBLASpreads voting power across many validators
Yield scheduleFixed rate7% decaying to 1% floorSustainable long-term economics
Ethereum bridgeActiveRemoved pending auditWill return only after independent security review
Min gas priceVariable1 Gwei enforcedProtects network from spam
📊 Performance

By the Numbers

<3.7s
True Finality
>5,000
TPS Throughput
~4.7s
PBFT Block Time
15/24
Consensus Quorum
63M
DAG Gas Limit
630M
PBFT Gas Limit
~40%
DB Compression
100%
EVM Compatible