A blockchain network upgrade can change transaction rules, software requirements, wallet behavior, or exchange availability. This reusable checklist explains what to do before a fork or protocol change, how responsibilities differ between exchange and self-custody users, and how to verify your holdings afterward without relying on rumors or rushed decisions.
Overview
Blockchain upgrades are coordinated changes to the software or rules used by a network. Some are routine protocol improvements that do not require ordinary users to take action. Others may be contentious forks that create two competing chains, or hard forks that make older software incompatible with the upgraded network.
The word “fork” does not automatically mean that holders will receive a new asset or that a profit opportunity exists. The practical effect depends on the network, the upgrade design, the wallet or exchange you use, and whether the service supports the relevant chain. A token may also be represented differently across networks, so checking the correct chain and contract or asset identifier is essential.
Before acting, identify five facts:
- What is changing: Determine whether the event is a routine upgrade, a hard fork, a chain split, or a migration to a new token or network.
- When it is expected: Upgrade timing may be expressed as a block height, an estimated time, or a maintenance window. Treat estimated times as subject to change.
- Which assets and services are affected: The native coin, tokens, smart contracts, bridges, exchanges, custodians, and hardware wallets may have different requirements.
- Who must act: Validators and node operators may need software updates, while ordinary holders may only need to wait for service support to resume.
- How success will be verified: Plan to check balances, transaction status, chain identity, and deposit or withdrawal availability after the upgrade.
Use official network announcements and the published notices of your exchange, wallet provider, or custodian as the starting point. Avoid treating social media posts, unsolicited messages, or third-party “claim” pages as instructions.
Checklist by scenario
If your crypto is held on an exchange or custodian
- Find the provider’s support notice and confirm the exact asset and network involved.
- Check whether deposits, withdrawals, trading, or transfers will be paused. Each function can have a different schedule.
- Look for the provider’s position on a possible new chain or token. Support may be announced later, limited to specific services, or not offered at all.
- Confirm whether you need to do anything. In many cases, the provider manages the technical upgrade, but this should not be assumed.
- Save account records before the maintenance window, including balances, transaction history, and any tax-lot information available through the platform.
- Do not send funds to an address supplied through an unsolicited message claiming to help you receive forked assets.
If service access is temporarily restricted, do not repeatedly submit transfers or attempt to bypass the pause. Wait for a clear status update, then verify the destination network before resuming activity. For broader due diligence on fees, withdrawals, and service policies, see How to Compare Crypto Exchanges.
If you use a self-custody software or hardware wallet
- Identify whether the wallet supports the upgraded network and the relevant asset after the change.
- Update wallet software only through the provider’s official app, website, or documented release channel.
- Back up your recovery phrase securely before making changes. Never enter it into a website, form, chat, or support request.
- Check whether the wallet displays the correct network, chain identifier, and asset contract where applicable.
- Expect possible delays in balances, fee estimates, or transaction history while the wallet’s data provider catches up.
- After the upgrade, test with a small transaction only when the network and wallet provider indicate that transfers are operating normally.
A wallet interface is not the blockchain itself. If the wallet shows an unfamiliar balance or warning, verify the transaction and asset on a reputable block explorer. The guide How to Read a Blockchain Explorer explains how to check confirmations, fees, and token contracts.
If you operate a node or validator
Node operators and validators have a more technical responsibility. Read the network’s release notes, confirm the required client version, check hardware and storage requirements, and understand the activation condition. Back up configuration files and record the current software version before upgrading. Follow the project’s documented procedure for stopping, updating, restarting, and monitoring the client. If you delegate staking, confirm whether the validator operator has acknowledged the change and whether any action is required from delegators.
If you use DeFi, bridges, or smart contracts
Review every application that holds, lends, stakes, or moves the affected asset. Pause unnecessary transfers around the maintenance window, especially when a bridge or protocol has not published a clear support statement. Do not assume that an application supports both sides of a chain split. Check whether approvals, wrapped assets, liquidity positions, collateral, or staking positions require separate treatment. For cross-chain transfers, consult Bridge Risk Guide: Safest Ways to Move Crypto Across Chains.
What to double-check
Keep a simple upgrade record so you can compare announcements with what actually happens:
| Item | What to record |
|---|---|
| Upgrade identity | Network name, asset name, upgrade label, and official announcement link |
| Timing | Block height or estimated date, including the time zone and any maintenance window |
| Service support | Exchange, wallet, custodian, validator, DeFi, and bridge policies |
| Transfer status | Whether deposits, withdrawals, trading, staking, or bridging are paused |
| Chain details | Network name, chain identifier, token contract, and native-asset symbol where relevant |
| Replay protection | Whether a transaction made on one chain could be accepted on another; follow official guidance |
| Required updates | Wallet app, hardware-wallet firmware, node client, validator software, or no user update |
| Post-upgrade checks | Balance, transaction confirmation, correct chain, and restored service availability |
Replay protection deserves particular caution. If a chain split occurs and transactions are not adequately separated, a transaction intended for one chain may create unexpected consequences on another. Do not experiment with replaying, splitting, or claiming assets unless the network and service documentation gives a clear, trusted procedure.
Also preserve records for accounting and tax purposes. A fork, migration, conversion, or distribution can affect the way you document acquisition dates, quantities, cost basis, and disposal activity. The correct treatment depends on your jurisdiction and circumstances, so retain notices, wallet records, and transaction hashes and seek qualified local advice when needed.
Common mistakes
- Moving funds at the last minute: Congestion, maintenance, or a wrong network selection can make a rushed transfer harder to resolve.
- Assuming every fork creates free money: A new chain may lack service support, liquidity, wallet access, or reliable price discovery.
- Using an unofficial claim tool: Requests for a seed phrase, private key, or unlimited token approval are strong warning signs.
- Updating from a sponsored search result or direct message: Confirm software sources through the wallet or network’s known official channels.
- Confusing a token migration with a blockchain fork: A migration may require exchanging an old asset for a new contract or depositing through a specified route.
- Ignoring chain identity: Similar names and symbols can represent different networks or contracts. Verify the destination before signing.
- Checking only the wallet screen: A delayed interface can be wrong or incomplete. Compare it with a block explorer and the provider’s service status.
- Forgetting third-party positions: Lending, staking, liquidity, and bridge deposits may follow separate rules from the wallet holding the underlying asset.
For general account and seed-phrase protection, use the Crypto Wallet Security Checklist. Treat any urgent request to connect a wallet, approve a transaction, or “validate” an account as untrusted until independently verified.
When to revisit
Revisit this checklist when a network publishes an upgrade proposal, assigns an activation block, changes its estimated schedule, or announces a possible chain split. Check again shortly before the maintenance window because exchange and wallet policies can change after the initial announcement. Recheck after completion when services begin restoring deposits and withdrawals.
A practical final review is:
- Confirm the upgrade has activated according to the network’s official status information.
- Confirm your exchange, wallet, validator, or application has published a current support update.
- Verify the network and asset identity before sending anything.
- Check your balance and recent transactions on the correct chain using a block explorer.
- Send a small test transaction only after normal operations are confirmed.
- Record any new asset, migration, conversion, or fee event for future reporting.
Network upgrades are technical events, not deadlines to trade. If the instructions are unclear, waiting for reliable confirmation is usually safer than acting on speculation. Keep this checklist with your wallet-security and portfolio-review routines, and update the network-specific details whenever the underlying project or service changes its guidance.
