What is Core Hermes Hardfork?

The Hermes hardfork for Core DAO was activated on the Core Testnet2 at 08:00:00 AM UTC on October 15, 2025, introducing updates to transaction speed, security measures, validator operations, developer tools, and staking processes

This upgrade, which draws from BNB Smart Chain version 1.5.12, sets the stage for a mainnet rollout. Upon mainnet launch, it could reduce transaction finality to about six seconds, expand the validator pool through new candidate roles, and enable features like code execution in externally owned accounts, potentially altering how the Core blockchain handles decentralized applications and staking rewards.

Core DAO and the Hermes Upgrade

The Hermes hardfork represents a protocol change that requires all nodes to update to maintain network consensus. Announced through official channels, including posts on X from Core DAO developers and staking providers like Everstake, the upgrade addresses specific operational needs identified in prior network performance.

The hardfork’s development involved testing on Testnet2, a separate environment for validating changes before mainnet deployment. An initial activation target of September 24, 2025, shifted to October 15 following additional preparations. This delay allowed for refinements, ensuring stability in features like fast finality and validator maintenance modes

Core DAO’s blog provided detailed guidelines, emphasizing that regular users face no immediate actions, while validators and full node operators must comply to avoid disruptions.

Key Features Introduced in the Hermes Hardfork

The Hermes upgrade incorporates several Blockchain Enhancement Proposals, or BEPs, each targeting distinct aspects of the network

BEP-126 implements fast finality, where transactions confirm in two blocks, typically within six seconds. This reduces the risk of chain reorganizations, where blocks might be discarded due to network inconsistencies, thereby improving reliability for users interacting with the blockchain.

BEP-127 introduces a maintenance mode for validators, enabling them to temporarily pause operations for software updates or hardware adjustments without incurring slashing penalties, which are deductions from staked assets for downtime. This feature supports network reliability by minimizing unplanned outages.

Under BEP-131, the hardfork introduces candidate validators, a preparatory role that lets new participants join safely. Candidates can observe and prepare before becoming active, which promotes decentralization by broadening the pool of validators beyond the current set.

BEP-341 permits validators to produce consecutive blocks, increasing overall throughput and decreasing latency in block production. This adjustment optimizes the consensus mechanism, enabling the network to process more transactions per unit of time.

BEP-410 establishes validator agents, entities that perform duties on behalf of primary validators. These agents handle tasks like block signing, enhancing uptime and operational flexibility, particularly for validators managing multiple responsibilities.

For developers

BEP-439 adds a precompile for BLS12-381 cryptography, facilitating efficient zero-knowledge proofs and threshold signatures. This supports complex applications requiring privacy or multi-party computations, common in decentralized finance protocols.

BEP-440 extends access to historical block hashes, allowing smart contracts to reference data beyond the previous 256 blocks. This enables on-chain randomness generation and historical analytics, useful for applications like lotteries or data verification.

BEP-441 allows externally owned accounts, or EOAs, to execute code, merging account and contract behaviors. This opens new programming patterns, such as automated account actions without separate contract deployments.

On the staking side, validators can now set commissions ranging from 0% to 100% on rewards from delegated CORE and BTC stakes. Channel partners, such as third-party staking platforms, can earn commissions on delegated assets, encouraging ecosystem integrations.

Additional updates include bug fixes, performance enhancements, and the deprecation of the Personal module in the Geth client. Operators are advised to switch to alternatives like Clef or command-line unlocks for key management.

Activation Timeline and Process

The Hermes hardfork went live on Testnet2 after a preparatory announcement on October 14, 2025. Core DAO’s developers confirmed the activation, noting successful integration at the specified timestamp. The mainnet launch remains pending, with stability assessments on the testnet informing the schedule

The upgrade aligns with Core DAO’s growth metrics, including a reported 2,800% year-over-year increase in activity, involvement from over 350 developers, and more than 100 decentralized applications deployed on the network. These figures, shared in official communications, underscore the platform’s expansion leading into the hardfork.

Guidelines for Validators and Full Node Operators

To align with the Hermes upgrade, validators and full node operators need to install version 1.0.21 of the Core software, available on GitHub. Documentation on Core DAO’s site outlines the process:

• Download the release
• Configure the node
• Ensure full synchronization with the chain.

For BEP-126’s fast finality, operators generate a voting key using Geth, requiring a password of at least 10 characters. They then update node configurations to enable voting and register the vote address on the Core Staking website. This setup is essential for participating in the new consensus rules.

Handling deprecated features involves replacing the Personal module with secure alternatives to manage private keys. Testing is recommended, with validators simulating operations on the testnet to verify compatibility.

Non-compliance risks falling out of consensus, which can lead to an inability to validate blocks or process transactions. Core DAO’s guidelines emphasize the importance of timely upgrades to prevent such issues, especially as the hardfork transitions to mainnet.

Potential Impacts on the Core Blockchain Upon Mainnet Launch

When deployed on mainnet, the Hermes hardfork could enhance transaction efficiency through faster finality and consecutive block production, potentially handling higher volumes without congestion.

• Security benefits from reduced reorganization risks and improved validator tools, like maintenance modes and agents, which could lead to better network uptime.
• Decentralization may increase with candidate validators, drawing more participants and distributing control
• Developer features, such as extended block hash access and code-enabled EOAs, could support sophisticated BTCfi applications, integrating Bitcoin assets more seamlessly.
• Staking changes, including adjustable commissions, may influence reward distributions as validators and partners optimize rates to attract delegators.

Overall, these updates aim to refine the Core blockchain’s operations, addressing scalability and usability in a BTCfi context.

Conclusion

The Hermes hardfork on Core DAO’s testnet introduces targeted improvements in transaction processing, validator management, and staking mechanics, drawing from established BNB Smart Chain elements. These changes, detailed through BEPs like fast finality and candidate validators, address specific network needs for efficiency and decentralization

Upon mainnet launch, they will support Core’s BTCfi focus by enabling quicker confirmations and flexible operations. In the meantime, Validators should prioritize upgrades as outlined in official guidelines to ensure smooth integration

To conclude, this upgrade reinforces the blockchain’s technical foundation, highlighting the importance of protocol evolution in maintaining performance and security.

Sources:

• Core DAO Official Blog:
• Core DAO Developers on X:
• Everstake on X: