The Ledger
Shentu Sets Mandatory v2.20.0 Upgrade for Block 31,812,210
Shentu’s release notes say validators and full-node operators must upgrade to v2.20.0 at block 31,812,210, scheduled for approximately 15:50 UTC on October 29, 2026. The instructions direct operators to wait for the target height, stop the shentud daemon, replace its binary and restart it with v2.20.0.

Block 31,812,210 is the upgrade checkpoint
Shentu’s v2.20.0 release notes designate the upgrade as mandatory for all validators and full-node operators. The release schedules it for block height 31,812,210, approximately 15:50 UTC on October 29, 2026. It identifies the block height as the point operators should wait for before carrying out the listed upgrade steps.
Source github.com
The published time is approximate; the release notes do not give a more precise clock-time estimate. The instructions state a sequence tied to the network reaching the target height: wait until that height, stop the running shentud daemon, replace its binary with the v2.20.0 version, then restart the daemon using that version. The release does not direct operators to switch binaries before the specified height.
Release notes require a binary replacement
The requirement covers both validators and full-node operators. The release does not limit the instruction to validators or to nodes involved in producing blocks. It identifies the replacement software as v2.20.0 and names shentud as the daemon to stop and restart.
The four listed steps set out the order of operations. First, operators wait for block 31,812,210 to be reached. Second, they stop the running daemon. Third, they replace the binary with the v2.20.0 version. Fourth, they restart the daemon with that version. The sequence, as written, places the stop, replacement and restart after the target height is reached.
The notes specify replacing the binary and restarting the daemon; they do not describe a rolling upgrade, an alternative installation method or a contingency procedure. Nor do they state what happens if a node is still running an earlier version after the target height. The release’s operational direction is limited to the stated height and the four-step switch.
The v2.20.0 page gives no changelog
The v2.20.0 section of the release page provides a timeline and upgrade instructions, but no technical changelog describing code changes. It therefore establishes the required version, which operators are covered, the scheduled block height and the daemon replacement procedure. It does not explain what has changed in the software itself.
For users and operators, the release page presents the upgrade as a required network software switch rather than an optional update. Its stated checkpoint is block 31,812,210; its time estimate is approximately 15:50 UTC on October 29. The notes provide no second clock-time estimate or further explanation of the scheduled time.
Operators are directed to follow the listed sequence
Before the target height, the release’s first instruction is to wait. Once the chain reaches block 31,812,210, operators are directed to stop the existing shentud process, install the v2.20.0 binary in its place and restart the daemon with the new version. Those are the complete upgrade steps stated in the release notes.
The page does not add separate procedures for validators and full nodes, and it does not set out a different schedule for either group. Both are included in the mandatory-upgrade notice and the same binary replacement instructions. The announcement’s published milestone is the target block height, accompanied by an approximate UTC time.
Sources
- Original source · Release notes GitHub — shentufoundation/shentu releases github.com