Shardeum applies the v1.1.0 plan at height 7,927,860
Shardeum applied v1.1.0 at block 7,927,860 on October 13. Public blocks show a 12-minute gap, not the halt of one to two hours venues were told to plan around.
Shardeum (SHM) applied upgrade plan v0.4.0-to-v0.6.3 at block height 7,927,860 at 06:07:59 UTC on October 13, 2026, seven minutes and 59 seconds after the 06:00 UTC estimate. From height 7,927,848 to 7,927,879, public CometBFT times show one gap longer than 15 seconds: 12 minutes and 26.5 seconds, between height 7,927,861 at 06:08:05 UTC and height 7,927,862 at 06:20:31 UTC.
The clock and the height were never the same instruction. The October 6 blog, updated on October 9, asked exchanges to suspend SHM deposits and withdrawals from about 02:00 UTC. A Telegram post on October 12 repeated a centralised exchange (CEX) pause at 02:00 UTC, an estimated halt at 06:00 UTC, and a window of one to two hours at that height. Both say the trigger is height, so the clock can slip. A four-hour deposit freeze around an estimate, beside a public gap under 13 minutes, freezes an asset that is already sealing blocks.
Shardeum's status line lagged the tip. At 06:23 UTC, just under three minutes after height 7,927,862, Telegram still described the network as halted and told validators to start v1.1.0. At 06:54 UTC the channel said block production had resumed. At 07:18 UTC rpc.shardeum.org was at height 7,928,464, block time 07:18:20 UTC, and not catching up. The average interval from 7,927,862 to that tip was about 5.8 seconds, so no second long stop fits. The applied-plan record is 7,927,860, and the current plan is null.
No post names an exchange that paused or restored SHM. The blog tells exchanges, remote procedure call (RPC) providers, indexers, custodians and bridges to be online before the estimate, and to reopen deposits only after their own node is upgraded, synced, and normal operation is confirmed.
The Shardeum network is live on v1.1.0, and block production has resumed.
That sentence is the 06:54 UTC Telegram post. No named executive is on the record. Cosmos EVM v0.6.3, published on September 3, 2026, says: "This release contains important security fixes. We recommend all chains upgrade to this patch release as soon as possible using a coordinated upgrade." The note calls the release state-breaking. Shardeum's v1.1.0 release of October 1 carries those fixes forward from v1.0.2 and states: "Nodes will crash if there is a version mismatch." Cosmovisor must use the name v0.4.0-to-v0.6.3. The binary is v1.1.0.
Where the client break actually sits
The break is narrower than an Ethereum Virtual Machine (EVM) outage. The release moves the dynamic-fee extension from /cosmos.evm.types.v1.ExtensionOptionDynamicFeeTx to /cosmos.evm.ante.v1.ExtensionOptionDynamicFeeTx, and the old URL is rejected from the upgrade height. Ethereum-format transactions are unaffected. MetaMask, ethers, viem, Hardhat and other JSON-RPC clients are outside the warning. Cosmos-native senders that still attach the old extension are not. That inverts Solana's 4,096-byte transactions, opt-in to send and not to read. Here the JSON-RPC path keeps its shape.
What the yes tally does not prove
Governance proposal #1, "Upgrade Shardeum mainnet to v1.1.0", ran from 10:30 UTC on October 6 to 10:30 UTC on October 9 and passed. Yes is 759,659,283.2 SHM. Abstain, no, and no-with-veto are zero, matching the October 6 blog. Bank metadata gives SHM 18 decimals, and the raw yes count divided by 10^18 rounds to that figure. Tally parameters set quorum at 33.4% and a pass mark of 50% of participating voting power. The blog's '100% Yes among participating voting power' is that second test, not a holder census.
Against 1,905,716,315.20 SHM in the bonded pool on the October 13 query, yes is 39.86% of bonded stake. The pool is not the October 9 snapshot, so the ratio is not turnout. A delegator who does not vote inherits the validator's vote. Stake absent from the tally is not a recorded no. Custodians who delegate take that default, as when Hyperliquid Strategies stakes 72.5% of its HYPE to its own validator, or when BNY Mellon adds staking while Galaxy runs the validators.
What desks should still refuse to assume
v1.1.0 is a state migration, not a binary swap. The release says v0.5.0 moved EVM coin data into a store this chain's genesis never filled, and the handler backfills it. The tip RPC still advertised CometBFT 0.38.19 at 07:18 UTC, while the release lists cometbft v0.38.21. One banner does not name the binary other peers run. The applied-plan height does.
SHM deposits and withdrawals were supposed to reopen only after a venue's own node was on v1.1.0, synced, and normal operation was confirmed. Cosmos-native senders on the old dynamic-fee URL should now fail at broadcast. Ethereum-format transactions should not.
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.
Reporting by Karthik Subramanian. Filed 13 October 2026, 12:14 GMT.
Digital Assets Correspondent
Karthik Subramanian is a founder, writer, and technology consultant with nine years in the crypto ecosystem.
