The Core blockchain is set for the Hermes Hardfork activation, a major upgrade bringing faster finality, enhanced validator operations, advanced developer tools, and commission support for both CORE and BTC staking.
Following a successful activation on Core Testnet2 (Oct 15, 2025, 08:00 UTC), the Mainnet activation is scheduled for November 25, 2025, at 08:00 UTC.
Activation Timeline
- Core Testnet2: October 15, 2025 – 08:00 UTC
- Core Mainnet: November 25, 2025 – 08:00 UTC
What’s New in Hermes Hardfork
Hermes delivers key protocol-level improvements across speed, validator flexibility, and developer capabilities.
Key Highlights
- Fast Finality (BEP-126): Transactions finalize in ~6 seconds (2 blocks).
- Validator Enhancements:
- Maintenance mode (BEP-127)
- Candidate validator onboarding (BEP-131)
- Consecutive block production (BEP-341)
- Validator agent support (BEP-410)
- Developer Upgrades:
- BEP-439: Adds BLS12-381 cryptography for advanced dApp use cases
- BEP-440: Access to historical block hashes for improved randomness and analytics
- BEP-441: EOAs with executable code, expanding dApp design possibilities
- Commissions:
- Validators can set 0–100% commission on staking rewards.
- Channel Partners can earn commissions on delegations made via their platforms.
- Merged Up to BNB Smart Chain v1.5.12: Enhanced compatibility and performance.
Network Impact
- Validators: Improved reliability, scalability, and flexibility.
- Developers: More powerful smart contract and cryptographic capabilities.
- Users: Faster, more secure transactions and seamless dApp experiences.
Action Required
For Validators & Full Node Operators
This is a mandatory upgrade to v1.0.22 before November 25, 2025, 08:00 UTC.
Failing to upgrade will cause your node to fall out of consensus and stop producing blocks.
Upgrade Steps:
- Download v1.0.22 from the official Core Releases GitHub.
- Follow the instructions for upgrading geth client provided in the official documentation.
- Verify your node is synced and functional with the new finality and block production rules.
- Configuring for BEP-126: Validator nodes must comply with the official guidelines after upgrading their geth client to the latest release to ensure compatibility with the fast finality upgrade. For more details, refer to the detailed guidelines for the validator and full nodes.
Important Configurations:
- BEP-126 (Fast Finality): Adjust monitoring for stricter finality enforcement.
- BEP-127 (Maintenance Mode): Learn proper entry/exit to avoid penalties.
- BEP-341 (Consecutive Blocks): Ensure infra supports multiple block production.
- BEP-410 (Validator Agent): Configure and test if applicable.
For Developers & dApp Teams
No breaking changes expected for most wallets or dApps, but testing is highly recommended.
Recommended Actions:
- Test on Core Testnet2.
- Update tooling for new client compatibility.
- Review and test contracts relying on:
- BLS cryptography (BEP-439)
- Historical block access (BEP-440)
- EOAs with code (BEP-441)
- Reassess any backend logic tied to:
- Block hashes or randomness
- Finality assumptions
- Account behavior differences (EOA vs. contract)
For General Users
No action required — your wallets and dApps will continue to function normally.
Why Upgrade?
Upgrading ensures uninterrupted participation in the network, access to new features, and alignment with the latest Core protocols.
Failing to upgrade may result in syncing issues or node disconnection.
Resources
The Hermes Hardfork marks a major milestone for Core — unlocking faster finality, advanced validator operations, and next-generation developer tools to power the future of dApps.