What is Xone Epoch
With the successful activation of the new epochs
module via hard fork at height # 6397023
, Xone Chain now adopts a standardized and modular Epoch system, inspired by Evmos Epochs (opens in a new tab), enabling flexible, composable, and on-chain managed time cycles.
The upgraded module provides a generic time cycle scheduler for on-chain logic, supporting dynamic triggering of network-level events (rewards, validator updates, governance, etc.) at the end of each epoch, all via configuration and without requiring hardcoded logic.
Definition and rules of Epoch
What is Epoch?
An Epoch is a recurring period defined by block height intervals, during which certain scheduled logic is triggered. The Epochs module manages multiple named epoch identifiers (e.g., day
, staking
, distribution
), each with independent cycles.
- Block generation time: ≈ 1.3 second/block
- Natural time span:
hour
= 1 H (3600s)
day
= 1 D (86400s)
week
= 7 D (604800s) - Execution: Registered hooks (
BeforeEpochStart
,AfterEpochEnd
) are triggered automatically
Dynamic periodicity: At the end of each Epoch, the network will automatically trigger the preset on-chain operations (such as reward settlement, validator rotation) and start a new cycle. This design makes the operation rhythm of Xone Chain clear and regular.
Core rules of Epoch
Parameter | Value | Description |
---|---|---|
Epoch Identifier | day | Default epoch name; custom identifiers can be added. |
Epoch Interval | 86400s | 1 Days. |
Current Epoch Number | Dynamically increasing | Can be queried on-chain using module API. |
Hooks | BeforeEpochStart /AfterEpochEnd | Trigger staking, distribution, governance logic. |
Core functions of Epoch
Reward distribution and staking economy
Periodic reward settlement: Staking rewards, transaction fee sharing, etc. of all network participants are settled and distributed uniformly at the end of each Epoch. Example: If you stake tokens in Epoch #100
, the rewards will be credited to your account at the end of Epoch #100
; you can also understand it as settlement at the beginning of Epoch #101
.
Transparent and verifiable: Users can track Epoch progress and expected returns in real time through block browsers.
Validator (Nodes) rotation
Decentralized rotation mechanism: At the end of each Epoch, Xone Chain selects validators for the next cycle based on staking weights and random algorithms to prevent power concentration.
Fairness: New validators need to wait for the Epoch switch to take effect.
Security: Frequent rotation reduces the risk of long-term attacks.
Protocol governance and upgrades
On-chain governance window: Major protocol upgrades or parameter adjustment proposals (such as handling fee rates, inflation models) must be voted on within a full Epoch cycle and take effect in the next Epoch. Example: If the proposal is passed in Epoch #101
, execution will start from Epoch #102
.
Network status snapshot
Checkpoint: A chain status snapshot is generated at the end of each Epoch to facilitate fast synchronization of light node and verification of data integrity.
🔧 What Changed Compared to Pre-Upgrade Epoch Logic?
Aspect | Old Logic | New Module |
---|---|---|
Epoch definition | Fixed block interval logic embedded in core code. | Fully modularized with named epochs. |
Trigger logic | Tightly coupled with staking/distribution. | Decoupled with hook-based logic. |
Customizability | Hard to change (requires code updates). | Fully configurable via params or governance |
Usability | Single-purpose (staking/reward). | Multi-purpose, reusable for multiple modules. |
Governance | No control. | Epoch interval and hook logic can be governed. |
🚀 Benefits of the New Epochs Design
- High Customizability: Support for multiple epoch identifiers and parameters.
- On-Chain Flexibility: Epoch behavior is configurable and upgradeable via governance proposals.
- Modular Hooks: Modules can independently register to respond to epoch changes.
- Predictability: Clear periodic cycle simplifies application behavior planning.
Comparison with Epochs of other blockchains
To help understand the Epoch design of Xone Chain, the following is a comparison of similar mechanisms of mainstream public chains:
Chain | Epoch | Core Purpose | Design Features |
---|---|---|---|
Solana | ~2-3 D (dynamic adjustment) | Inflation reward distribution, validator weight update | Dynamic periodic adaptation to network performance changes |
Ethereum 2.0 | 32 blocks (~6.4 Minutes) | Validator Committee Rotation, Finality Confirmation | High-frequency coordination of short-term adaptation to PoS consensus |
Cardano | 432,000 blocks (~5 D) | Staking Rewards Distribution, Slot Leader Election | Natural time alignment, emphasizing the pledge economic cycle |
Xone Chain | 3600s /86400s /604800s | Rewards distribution, validator rotation, governance effectiveness | High Customizability、Flexibility、Modular、Predictability |
📡 Querying Epoch Info (via gRPC or Http)
grpcurl -plaintext https://gateway.xone.org evmos.epochs.v1.Query/EpochInfos
View Details
FAQ
Q1: How does this affect reward distribution and staking?
All staking rewards and updates are now managed through the epochs
hook system. Rewards are still settled at the end of each epoch, but the underlying trigger is now cleaner, more secure, and maintainable.
Q2: Can I define my own Epochs?
Yes. Developers can register new epoch identifiers (e.g., weekly
, custom
) and associate them with specific modules via hooks.
Q3: Will Epoch intervals remain fixed?
Yes by default, but they can be modified via governance proposals without code upgrades.
The new Epochs module marks a significant milestone in Xone Chain’s modular architecture evolution. It enhances network coordination, simplifies scheduling logic for future applications, and ensures better governance agility — all while maintaining predictable and user-friendly block-level timing.
For any help or support, please contact us:
Support: [email protected]
Official: [email protected]
Business: [email protected]
News: Medium
Community: Telegram | Twitter | Discord | YouTube | Reddit | ChatMe | Github