Abonnieren Sie unseren Telegram-Nachrichtenkanal Cryptoage und bleiben Sie über die neuesten Trends auf dem Laufenden.
Bergbau, Airdrops, Handel, Leitfäden, Technologien, Investitionen – es ist alles da!!!
Nexa's Tailstorm date has passed, but Hard Fork 2 is still not activated: what NexaPoW miners should know
The official specification of Nexa still lists November 1, 2026 as the mainnet activation time of Hard Fork 2, the upgrade that brings Tailstorm. The date has passed, but the switch has not flipped: on November 1 the Nexa team answered a mining-client developer that Tailstorm is not yet activated and that there are no official mining fixtures or pool protocol changes for it.
Why the date did not trigger the fork
Full Node 2.2.0.0, released on September 2, already contains the Tailstorm code, but the team described it as a preparatory release: the hard fork will only be activated by the next release. Version 2.2.0.0 switched on just one change right away, rolling checkpoints, which make a node refuse any reorganization deeper than 200 blocks. No new release with activation has been announced so far, and the team says future information will come through official Nexa channels.
What Tailstorm will change for mining
- Each 2-minute block becomes a summary block that ties together 120 proof-of-work subblocks on mainnet, so a subblock appears roughly every second.
- A summary block is backed by 120 independent solutions instead of one, which the spec says reduces the variance of block discovery and of mining revenue.
- After activation, legacy blocks are no longer valid, so pools and solo miners will have to run updated nodes and software that understands subblocks.
- The floor of the adaptive maximum block size rises to 12 MB.
What NexaPoW miners should do now
Nothing changes for now: the network runs on the current NexaPoW rules, and pools work as before. Keep the node and mining software up to date, and treat any pool or miner that claims Tailstorm support with caution until the official activation release appears. When it does, check that your pool has upgraded before the fork, otherwise its blocks will be rejected.