Protocol upgrades change the rules that blockchains use to validate transactions, produce blocks and coordinate network participants. This beat covers hard forks, soft forks, scheduled mainnet releases and unplanned chain splits, from major redesigns of Ethereum to Cardano deployments such as Leios and Van Rossem. It also follows upgrades that affect execution, consensus, governance and security, including Solana’s stake-weighted voting and work around Firedancer and Alpenglow, Starknet’s post-quantum roadmap, and releases such as Base’s Beryl upgrade. These changes matter because even a technical update can alter fees, throughput, validator requirements, smart-contract behavior or the assumptions on which wallets, bridges and exchanges rely.
Zipp tracks each upgrade from proposal and testnet work through client releases, activation and post-launch monitoring. Our coverage distinguishes a long-term roadmap from approved code, and a scheduled activation from a completed deployment. We examine whether node operators must update software, how consensus thresholds are measured, which features are included or deferred, and whether validators or users face compatibility risks. When a fork could create competing histories, we follow chain support, replay protection, asset treatment and infrastructure readiness rather than treating every software release as a new token event. For networks associated with ETH, ADA, SOL, BTC, XRP and UNI, the focus remains on what changed at protocol level, who must act, and what evidence shows that the upgraded network is operating as intended.
The proposal puts Polygon’s recovery process and the role of a mainnet hard fork in focus after funds were stolen from Polymarket and Binance.
NU7 will retire the transaction format needed to spend Sprout funds, reducing legacy software complexity while leaving any coins behind potentially inaccessible indefinitely.
The correction separates token-destruction permissions from issuance, while also bringing accounting fixes for planned lending and pooled-asset features.
The plan would transfer blocked funds to recovery addresses without changing POL's total supply, putting governance and hard-fork safeguards in focus.
The speed gains arrive alongside a dispute over ZEC grant funding and recent price weakness, putting network improvements against questions about governance and investor confidence.
The Ethereum exploit exposed how signed wallet permissions can put existing funds and later deposits at risk, while Binance investigates how the attacker obtained authorization.
Deposits remain operational, but the withdrawal pause puts attention on service reliability and the timing of a return to normal operations.
The Jenner hard fork is live on BSC testnet, putting a defined share of block gas toward payment transactions ahead of any mainnet deployment.
The fix keeps validator deposits separate from builder funds, but client integration and a new Hoodi test date still stand between Glamsterdam and mainnet.
Shorter slots cut the time available for each trade, but sampled early-buy and sandwich rates show speed alone has not removed the extraction problem.
The funding model has supported a progression from Sprout and Sapling to Orchard and Ironwood, keeping developer incentives central to Zcash's privacy roadmap.
Polkadot's July upgrade cut unstaking from 28 days to about two, shrinking the window to rescue funds from compromised wallets just as the breach came to light.
The cancellation of Monday's Hoodi testnet activation signals the risks are live enough to halt the schedule, not just flag for later review.
EIP-8037's gas accounting changes raised compatibility flags with existing mainnet smart contracts, forcing developers to pull the October 26 activation and cancel the planned 200M gas limit increase.
Validator support slipping below the 29-node threshold forced a last-minute postponement, adding governance risk to a token already under pressure from a broad liquidation sweep.
A deal at that valuation would hand Visa direct ownership of one of crypto's most widely used institutional custody and tokenization platforms, reshaping how the card giant competes in digital asset…
The launch consolidates Dogecoin's developer effort under a single entity, signaling a shift from meme-driven price action toward infrastructure that can support real-world adoption.
The activation block is now locked in, giving node operators and wallet developers a concrete deadline to coordinate compatibility before the upgrade goes live.
Faster finality can let payment apps confirm transfers sooner without requiring wallet, fee or application changes.
Support has recovered to 31 of 35 validators, above the 29-vote threshold, but the patch must complete a fresh 14-day approval countdown.
A hard fork introduces rules that older node software may reject, so participants generally need to upgrade to remain on the same chain. A soft fork tightens existing rules in a way that can remain compatible with non-upgraded nodes, although miners or validators may still need to adopt it for activation.
No. Most hard forks are coordinated upgrades in which users, validators and infrastructure providers continue following one canonical chain. A separate asset emerges only if competing rule sets retain meaningful support and produce persistent, independent chains.
Check the announced activation condition, compatible client versions and block or epoch data from independent explorers. A completed activation should also be supported by stable block production, validator participation and status reports from core infrastructure providers.
Exchanges may pause transfers to update node software and avoid processing transactions while finality or chain stability is uncertain. Trading can continue internally even when onchain deposits and withdrawals are temporarily unavailable.
Crypto News
CoinDesk
WuBlockchain
CoinTelegraph
CryptoSlate