Network upgrade tracker

Find the upgrade, then find the person who had to act.

Filter 13 activated milestones across five networks. Each record separates ordinary holder guidance from developer and node-operator work, and remains readable without JavaScript.

13 milestones shown

Scaling

Ethereum · Dencun

Blob transactions lowered the data cost path for rollups

What changed: Dencun activated proto-danksharding through EIP-4844 and combined execution-layer Cancun changes with consensus-layer Deneb changes.

Holder action: None for ordinary ETH or wallet balances; no token conversion was required.

Technical action: Stakers and node operators had to run compatible consensus and execution clients before epoch 269568. Rollup teams could integrate blob transactions.

Ethereum Foundation announcement
Governance

Cardano · Chang

On-chain governance entered its bootstrap phase

What changed: Chang began the Conway ledger era and introduced the first stage of Cardano's CIP-1694 governance framework.

Holder action: ADA did not need to be swapped. Participation choices depended on the holder's wallet and governance plans.

Technical action: Stake-pool operators and ecosystem infrastructure needed compatible node and application releases.

Cardano hard-fork timeline
Fees

Avalanche · Etna

Independent Avalanche L1 operation became less capital intensive

What changed: Etna implemented the network changes associated with Avalanche9000, replacing the previous recurring validator cost model for sovereign L1s with a continuous fee.

Holder action: None for ordinary AVAX custody. Users still needed to respect any exchange maintenance window.

Technical action: Validators needed AvalancheGo 1.12.0 or later; L1 builders had new operating and interoperability choices to evaluate.

Avalanche Etna overview
Governance

Cardano · Plomin

The full governance action set became available

What changed: Plomin completed the transition to Cardano's on-chain governance framework, enabling constitutional committee, DRep and stake-pool roles to participate under the new rules.

Holder action: No asset migration was required. ADA holders could choose whether and how to delegate governance power.

Technical action: Wallets, explorers, governance interfaces and operators needed support for the Conway-era rules and certificates.

Cardano Plomin documentation
Security & validation

Arbitrum One · BoLD

Validation became permissionless with a bounded dispute delay

What changed: BoLD replaced the previous allowlisted validation model and was designed to bound delay attacks in the dispute process.

Holder action: None for ordinary ETH or token balances on Arbitrum One; no migration or claim was part of the upgrade.

Technical action: Validators and infrastructure teams needed to understand the new challenge protocol and deployment boundary.

Arbitrum Foundation AIP
Fees

Avalanche · Fortuna

C-Chain dynamic fees gained a much lower minimum

What changed: Fortuna lowered the C-Chain minimum base fee to one wei, allowing demand to determine fees across a much wider range.

Holder action: No token conversion. Transaction costs could change, so users still needed to check the fee presented by the wallet.

Technical action: Wallet, RPC and application teams needed to avoid hard-coded fee assumptions and use current fee data.

Avalanche fee documentation
Performance

BNB Smart Chain · Lorentz

Block intervals fell from three seconds to 1.5 seconds

What changed: Lorentz shortened BSC block production time and adjusted networking behavior to support faster confirmation.

Holder action: None for ordinary BNB balances. Users could encounter temporary exchange deposit or withdrawal pauses around activation.

Technical action: Validators, full nodes, exchanges and RPC providers needed the specified release before the mainnet fork height.

BNB Chain Lorentz announcement
Developer features

Ethereum · Pectra

Accounts, validators and blob capacity changed together

What changed: Pectra bundled execution and consensus improvements, including EIP-7702 account capabilities, validator balance changes and increased blob throughput.

Holder action: No ETH conversion or required wallet transfer. New account features only mattered when a wallet deliberately exposed them.

Technical action: Node operators upgraded both clients; wallet, staking and application teams reviewed changed account and validator behavior.

Ethereum Foundation announcement
Performance

BNB Smart Chain · Maxwell

Block intervals fell again, from 1.5 seconds to 0.75 seconds

What changed: Maxwell continued BSC's performance work with sub-second blocks and related consensus and networking adjustments.

Holder action: None for ordinary balances. A faster chain did not remove the need to wait for a venue's own confirmation policy.

Technical action: Validators and infrastructure operators needed the compatible client and had to verify their systems could handle the faster cadence.

BNB Chain Maxwell announcement
Scaling

Ethereum · Fusaka

PeerDAS expanded the path to greater blob capacity

What changed: Fusaka introduced PeerDAS and other execution and consensus changes intended to let nodes verify blob availability without downloading every blob.

Holder action: No ETH swap, claim or balance migration. Messages asking holders to “upgrade ETH” were not part of the protocol process.

Technical action: Node operators updated clients; rollups and infrastructure teams prepared for the changed data-availability environment.

Ethereum.org Fusaka guide
Scaling

Ethereum · BPO1

The blob target increased after Fusaka activation

What changed: The first blob-parameter-only fork raised Ethereum's blob capacity without bundling a full protocol upgrade.

Holder action: None. The change affected network data capacity rather than ETH ownership or wallet balances.

Technical action: Operators remained on compatible clients and rollup teams monitored capacity, pricing and network behavior.

Ethereum Fusaka and BPO schedule
Scaling

Ethereum · BPO2

A second parameter-only fork increased blob capacity

What changed: BPO2 applied the next planned blob-parameter adjustment after the network had observed Fusaka and BPO1.

Holder action: None. It did not create a new ETH asset or require a wallet migration.

Technical action: Rollup, node and monitoring teams tracked the higher data-capacity settings and current client guidance.

Ethereum mainnet fork timeline
Developer features

Cardano · van Rossem

Protocol version 11 extended ledger and Plutus capabilities

What changed: The van Rossem hard fork activated protocol version 11 at epoch 644 with ledger, governance and smart-contract improvements.

Holder action: No ADA swap was required. Holders only needed to follow a provider notice if a service paused transfers.

Technical action: Stake-pool operators, wallets, exchanges and application teams needed compatible releases and updated feature assumptions.

Cardano hard-fork timeline