DigiDollar Thaw Day is past DigiByte block 24,490,000

DigiDollar's mainnet Thaw Day is DigiByte (DGB) block 24,490,000, and that block is already on the canonical chain. DigiExplorer's block record for hash b334947e84c3743975645635850b1c7b941da695fd45945281fce0003e9d2370 is height 24,490,000, timestamped 01:38:27 UTC on November 2, 2026. CryptoID's block page prints the same hash and the same time. DigiByte Core v9.26.6, published on October 1, 2026, says mainnet activation is that height rather than a calendar date, and it keeps an estimate of around November 1 only as a historical line from the RC1 notes. The block's own timestamp falls early the next day, which is what a height rule does when blocks arrive more slowly than the note assumed.

Other networks have used a numbered gate rather than a clock this autumn. Shardeum applied its v1.1.0 plan at height 7,927,860, and Filecoin's Solstice upgrade is live at epoch 6,470,279. DigiDollar (DD) adds a second job on the same block, because DigiDollar checks switch there while a node that only relays DGB still has to accept the blocks that follow. The final section of the release states the duty that applied before the height.

All full-node and mining operators must upgrade before mainnet block 24,490,000, including operators who do not use DigiDollar.

What that instruction covered

The following sentence says older software can disagree about valid blocks after the height, and the notes record that testnet26 activated Thaw Day at block 432,100. A normal upgrade from a working RC2 node keeps its chain data and the DigiDollar block history the node still needs.

Related:Dijkstra hard fork stays undated as node 11.2 advances

The release pairs the warning with a working order: back up wallets and configuration, download the final build, verify the published checksums, stop the old daemon normally, replace the program, restart, and confirm that the version is v9.26.6 once synchronizing has finished. The command getdigidollardeploymentinfo reports the scheduled height and whether the tip or the next block uses the new rules. Five Guix packages and a SHA256SUMS file are attached.

Two clocks in the same tag

The tag's DigiDollar node operations guide still schedules mainnet Thaw Day at 24,490,000 and estimates November 1, 2026. It describes the v9.26.6 development source, withholds a release-readiness announcement, and states that no public-network Thaw Day activation or sustained network test has been completed for that candidate. The release-notes file points to the combined notes, which call the RC1 calendar lines historical and say the block number starts the change. CryptoID and DigiExplorer agree on a narrower fact: block 24,490,000 is canonical, and on November 1, 2026 the height was still ahead of the tip because the block is stamped 01:38:27 UTC on November 2.

A coinbase at the switch

DigiExplorer records one transaction on the activation block and a DigiDollar transaction count of zero. CryptoID records one transaction and 247.93026605 DGB created, a coinbase figure rather than a run of mints, so the rule change lands in a block that carries no DD transfer. DigiExplorer's recent-block list, fetched on November 2, 2026, opened at height 24,491,385, timestamped 07:22:09 UTC. CryptoID's activation page that morning was current through block 24,491,384. The run from 24,490,000 at 01:38:27 UTC to 24,491,385 at 07:22:09 UTC is 1,385 blocks and five hours, 43 minutes and 42 seconds of production after the switch.

What the new checks require

The preserved RC1 section says Thaw Day replaces the old mint freeze with a price check on prices already stored in the chain. New mints still need an accepted oracle price, enough collateral and a price that clears the check, and a large swing can still pause minting. The height creates no tokens and leaves wallet balances as they were.

Pools, exchanges, oracle services and wallet backends share that upgrade list with miners and full nodes, and a client whose venue holds the keys is sent to the venue's own notice. The height sits in the public-network binary, so neither a miner vote nor a local setting moves it, and a delay would have required a replacement build installed before block 24,490,000. IoTeX's Zanzibar hard fork is the comparison for a desk that settles DGB: software left on the prior release can follow a different chain once the rule is live. The notes tell operators to compare block hashes at the same height and to finish recovery before settlement resumes. The observable check now is the version string a pool or an exchange is still serving against v9.26.6.

This article is informational analysis only and is not financial, investment, or trading advice. Cryptocurrencies are highly volatile and can lose substantial value rapidly. Past performance and historical patterns do not guarantee future results. Do your own research and consult a regulated financial adviser before making any investment decision.