The tweet was deleted by the author.
But we saved everything 🙂.
A blockchain is generally seen as a system that cannot simply be switched off as long as at least some participants continue supporting the network. Yet in 2026, several projects are preparing to shut down their own L1s. What happens to users' assets once a blockchain stops operating?
A recent example is Harmony. In September, the team proposed shutting down its Layer 1 entirely, recording the network's final state, and migrating ONE tokens to Ethereum.
View post on X Loading...
Such a scenario does not mean the token disappears along with the blockchain. When a network shuts down, what typically stops is the mechanism that allows participants to agree on its new state, while the transaction history and the asset itself can continue to exist in another form.
Harmony launched its mainnet back in 2019, but by 2026, maintaining its network had become a separate risk for the project.
Shortly before the shutdown proposal, the team suffered a major incident. In August, an attacker exploited a vulnerability that allowed transactions to be replayed and created around 3 trillion illegitimate ONE tokens.
The team decided to roll back the blockchain to its state before the attack.
The project already had a painful history with security. In 2022, the Horizon Bridge hack resulted in losses of around $100 million. Developers now explicitly link the idea of abandoning their own L1 to the growing difficulty of securing an independent network against state-backed groups and increasingly sophisticated automated attacks.
The proposed scenario looks almost like a predetermined date of death.
The network would produce its final block, after which its state would be frozen. The snapshot would include ONE balances, delegations, validator rewards, and other positions, while a new ERC-20 version of ONE would be issued on Ethereum and distributed to holders of the old coin.
Preserving token balances is relatively straightforward. Migrating an entire blockchain as a functioning economy is not.
Smart contracts, liquidity pools, NFTs, loans, and applications all depend on the state of a particular network. Harmony, therefore, warned that users would need to exit certain contracts and positions in advance because they cannot be automatically migrated to Ethereum.
ICON provides an even clearer example. Rather than switching off the network in a single day, the project is gradually stripping it of its economic activity.
In March 2026, ICON entered Economic Shutdown mode. ICX issuance stopped, rewards were discontinued and the number of active validators was reduced to seven, all controlled by the ICON Foundation.
The network continues producing blocks so holders can migrate ICX to the new SODA token.
View post on X Loading...
The final shutdown is scheduled for December 31, 2026. After that, transactions will no longer be possible, although the blockchain's history is expected to remain accessible in read-only mode. The window for migrating ICX to SODA will also close.In other words, a network can die economically long before its final block. New issuance disappears first, the number of validators and liquidity decline, and only at the end does the production of new blocks stop.
The network's history can remain as an archive. What changes is that participants no longer collectively update the blockchain's state.
A real-world example of a completed shutdown is BNB Beacon Chain. It was decommissioned not because the project failed, but because maintaining a two-chain architecture had become too complex and costly. Beacon Chain's functions were gradually moved to BNB Smart Chain.
The process took place in stages through several upgrades, with BNB Chain preparing the network for its final shutdown in advance.
View post on X Loading...
The network finally stopped operating in December 2024. After the last block, developers recorded its final state and created a cryptographic mechanism that allowed ownership of compatible BEP2 and BEP8 assets to be verified on BSC. Historical data was preserved separately.
But migration did not guarantee that every token would be saved. Assets that had not been prepared for migration to BSC could remain permanently locked. For some users, the death of a network therefore does not mean that the record of ownership disappears, but that they lose the ability to do anything with that record.
This is particularly complicated for DeFi. If a user simply holds a native coin at a regular address, the balance can be relatively easily included in a network snapshot. But funds held in a liquidity pool, loan, or complex smart contract may require a separate exit procedure or may be incompatible with the new network altogether.
That is why teams usually ask users to withdraw assets, close positions, and prepare for the final block well before a shutdown.
By 2026, this scenario is no longer unusual. ZETA holders backed a September proposal to abandon the project's own ZetaChain L1 and migrate the token to Solana. The initiative received support from 99.4% of participating tokens, although the migration itself will require a separate decision.
View post on X Loading...
Unlike Harmony, security is not the only reason here. The team wants to focus on a different product, making its own blockchain no longer an essential part of the strategy.
This changes the conventional idea of a native coin. As long as an L1 exists, such an asset is typically used to pay gas fees, stake, and help secure the network. After moving to Ethereum or Solana, the same ticker may survive, but its function becomes entirely different.
There are also more radical approaches. When winding down its old infrastructure, SX Network, for example, proposed recording holders through a network snapshot and providing eligible users with another form of compensation instead of simply migrating the old token on a one-to-one basis.
As we have seen, a project does not necessarily disappear when its network shuts down. The token can move to another blockchain, users can migrate, and the team can continue development on new infrastructure.
The final block is therefore not always the final stage in a project's life. It is much harder to determine when a blockchain itself can truly be considered dead: is stopping the validators enough, or does the network continue to exist as long as someone keeps running the old code?
Developers cannot delete every existing copy of a network. If some operators continue running the old code and can maintain consensus, the chain can technically continue to exist independently of the official project.
A blockchain shutdown is therefore not a binary state. So-called "zombie networks" can exist where development has largely stopped and liquidity and activity are minimal, but a handful of validators continue producing blocks.
An organized shutdown is different because most participants agree in advance to stop extending the shared history. Exchanges end support for the old standard, applications shut down or migrate, and validators stop producing new blocks.
In this sense, a blockchain does not die when its data disappears. It dies when participants stop collectively creating the network's next state.
This creates a paradox for the modern crypto industry. A project can abandon its blockchain while retaining its name, users, and token within someone else's infrastructure.
The death of an L1, therefore, increasingly does not mean the death of the project itself. Sometimes it is simply an acknowledgment that maintaining a separate consensus mechanism, validator set, and network security no longer makes economic sense.
The blockchain's history remains archived, while its coin may continue to exist on Ethereum or Solana. In modern crypto, the network itself can die—but the asset created for it does not necessarily have to.