HeLa Runtime (EVM)
HeLa Chain adopts a multi-layered architecture, deliberately separating consensus and runtime functionalities into distinct layers. This design provides modularity, security, and scalability — ensuring that the consensus engine and execution environment operate independently but cohesively.
At the core of this architecture lies the HeLa Runtime Layer, which has been purposefully engineered to be EVM (Ethereum Virtual Machine) compatible. This decision carries significant benefits for developers, projects, and the broader ecosystem.
EVM Compatibility
The HeLa Runtime Layer is fully Ethereum Virtual Machine (EVM) compatible. This compatibility is a deliberate design choice, enabling seamless integration with the vast developer and project ecosystem already established on Ethereum.
Key Advantages
Effortless Migration of Existing dApps The primary motivation behind this compatibility is to enable the effortless deployment of existing EVM-based projects onto the HeLa Chain. A substantial portion of decentralized applications (dApps) are written in Solidity, the most widely used programming language for smart contracts on Ethereum. EVM compatibility allows these applications to be deployed on HeLa Chain with little to no modification, lowering friction for adoption.
Faster Development Cycles Developers can leverage their existing skillsets, frameworks, and workflows. This reduces onboarding time, shortens the development lifecycle, and accelerates the creation of new projects and use cases on HeLa Chain.
Enhancing Existing dApps with HeLa Features Beyond compatibility, developers can enrich their existing Ethereum-based dApps by integrating HeLa’s unique platform-specific features. This unlocks opportunities for creativity and innovation without requiring teams to abandon their established tools.
Ecosystem Alignment
By introducing an EVM-compatible runtime layer, HeLa Chain creates a familiar and accessible environment for Ethereum developers to transition and build upon.
This alignment achieves two key outcomes:
Welcoming Ethereum’s Global Developer Community: The ecosystem can directly leverage the knowledge, resources, and momentum of one of the world’s largest blockchain developer bases.
Accelerated Ecosystem Growth: Lower entry barriers allow projects to deploy rapidly, driving experimentation, adoption, and the emergence of pioneering blockchain solutions.
In effect, HeLa’s EVM compatibility not only ensures continuity with Ethereum but also positions the platform as a hub of innovation, bridging the established Ethereum ecosystem with the new opportunities available exclusively on HeLa.
Block Production Specification
This describes the block production behavior in the Consensus Layer and Runtime Layer of the chain, including timing, transaction handling, and epoch transition mechanics.
1. Consensus Layer
Block Interval: The consensus layer produces a block every 5 seconds.
Transaction Requirement: Block production occurs independently of transaction availability. Empty blocks are finalized on schedule.
Determinism: This ensures a predictable and consistent chain growth rate of ~12 blocks per minute.
2. Runtime Layer
The runtime layer executes state transitions and produces runtime blocks subject to the following rules:
Block Frequency Constraint
Runtime blocks cannot be produced faster than the consensus block interval (1 block / 5s).
Transaction-Dependent Behavior
With transactions: A runtime block is produced every 5s.
Without transactions: No runtime blocks are produced unless triggered by an epoch transition.
3. Epoch Transition
Epoch Duration: 600 consensus blocks.
Nominal Epoch Length: 50 minutes.
Observed Duration: Due to propagation and scheduling delays, the effective duration is approximately 52 minutes.
During each epoch transition:
The runtime layer produces two empty runtime blocks, even in the absence of transactions.
These blocks are required to finalize committee member updates and ensure validator set correctness.
Therefore, if there are continuous transactions, runtime layer generate block every 5 second. If no transactions, runtime layer generate 2 block every 52 minutes.
Last updated