The name is not an accident. The mission is not a coincidence. Here's the full story behind EBLA.
"Ancient Ebla meant 'white stones' â think of this as our white stone. Not a white paper."
Most blockchain projects launch with a white paper â a dense document full of promises, economics, and governance structures written by teams who may later disappear. EBLA starts differently. Every letter in our name was chosen with purpose. The ancient city of Ebla ð ð·ð was one of the earliest known civilizations â built to last, built by its people, built on solid ground.
This is our white stone: a mark of identity, permanence, and ownership. Laid not by a foundation, not by VCs â but by every validator, developer, and community member who chooses to be part of EBLA.
Ethereum Virtual Machine compatible. Every Solidity contract, every wallet, every dev tool â works out of the box.
A Directed Acyclic Graph of blocks â parallel processing that breaks the single-chain bottleneck. Over 5,000 TPS by design.
A permanent, transparent record of truth. Owned by no one. Readable by everyone. Immutable by design.
Not assembled â architected. Every component from consensus to staking was designed to serve decentralization first.
Taraxa was a pioneering blockDAG Layer-1 â one of the first networks to prove that parallel block processing could work at scale. Technically advanced for its era, it shipped real EVM compatibility and a working mainnet.
The original Taraxa team stepped away. Development slowed, then stopped. For most projects, this is where the story ends â abandoned code, a dead Discord, and forgotten tokens.
Validators, developers, and believers who had built on Taraxa refused to walk away. They had a conviction: a truly decentralized network cannot die just because one team leaves. The code is open. The chain is public. The community endures.
The community forked the codebase, fixed what was broken, rebranded as EBLA, and relaunched. Just the community, the code, and the conviction to rise from the ashes.
Build out grants, tooling, documentation, and support for the next generation of dApps and protocols on EBLA.
Full on-chain voting for protocol upgrades, treasury decisions, and validator policies â by token holders, for token holders.
Public dashboards for network health, validator performance, and token flows (full transparency by default).
Expand the validator set, lower staking barriers, and ensure no single entity can ever hold meaningful network control.
There is no core team to wait for, no foundation to petition. If you believe in EBLA â you build it. Join the community and help lay the next white stone.