FEK is a next‑generation Layer‑1 blockchain designed to deliver low‑latency finality, predictable fees, and a best‑in‑class developer experience while maintaining strong decentralization and security. FEK prioritizes pragmatic engineering: an EVM‑first execution layer, a HotStuff‑style PoS BFT consensus for fast finality
Three gaps persist across popular chains: (1) inconsistent finality under stress; (2) opaque fee dynamics; (3) fragmented, hard‑to‑maintain developer stacks. FEK addresses these with a HotStuff‑derived BFT consensus tuned for low variance finality; fee shaping to keep UX stable; and a single, EVM‑first execution environment backed by ergonomic libraries and tooling.
Security first: Safety over liveness in ambiguous network partitions; clear slashing for equivocation.
FEK’s consensus is a partially synchronous, leader‑based BFT protocol inspired by HotStuff, delivering deterministic finality in two rounds of voting under healthy conditions.
Admission: Permissionless; validators self‑bond and satisfy minimum hardware/uptime requirements.
FEK aims to be a practical, performant, and evolvable base layer. By combining BFT finality with EVM familiarity and a modular data layer, FEK offers developers and users a predictable yet forward‑looking platform. This document focuses on how FEK works—not on economics or distribution. Future revisions will include finalized specs, DA adapter details, and hardening results from public testnets.
Learn MoreFEK is built for a world where blockchains must be both reliable infrastructure and open innovation platforms.
for consumer dApps, payments, and on‑chain coordination.
through safe, on‑chain governance and capability‑gated protocol changes.
A Modular, High‑Performance, EVM‑Compatible Layer‑1 Blockchain
FEK is a next‑generation Layer‑1 blockchain designed to deliver low‑latency finality, predictable fees, and a best‑in‑class developer experience while maintaining strong decentralization and security.
FEK is built for a world where blockchains must be both reliable infrastructure and open innovation platforms. In practice, that means: Fast finality for consumer dApps, payments, and on‑chain coordination. Predictable fees with an EIP‑1559‑inspired base‑fee model and congestion control. Developer familiarity via EVM compatibility and battle‑tested tooling.
Three gaps persist across popular chains: (1) inconsistent finality under stress; (2) opaque fee dynamics; (3) fragmented, hard‑to‑maintain developer stacks. FEK addresses these with a HotStuff‑derived BFT consensus tuned for low variance finality; fee shaping to keep UX stable; and a single, EVM‑first execution environment backed by ergonomic libraries and tooling.
Security first: Safety over liveness in ambiguous network partitions; clear slashing for equivocation. Simplicity where possible: Choose boring, proven components unless clear, measurable wins justify complexity. Modularity over maximalism: Clean interfaces for consensus, networking, and DA to evolve independently. Developer empathy: EVM compatibility, source‑map debugging, deterministic builds, and strong docs.
Full nodes: Validate blocks, execute state transitions, serve historical data. Validators: Propose and vote on blocks; required to run full nodes. Archival nodes: Retain full history; offer high‑throughput RPC and indexing endpoints. Light clients: Verify with succinct proofs (finality signatures + state commitments).
State DB: Key‑Value (RocksDB/LMDB class) with trie‑based state commitments (Keccak‑Patricia). Snapshots: Periodic state snapshots for fast sync; incremental pruning of old trie nodes. DA Adapter: Interface to plug external DA systems in future upgrades without breaking consensus.
