Crypto seems to have entered a period of unusually frequent farewells.
From BitMEX, which operated for 11 years and helped shape the crypto perpetual futures market, to Satori Finance, backed by leading investors including Polychain and Coinbase Ventures, one familiar name after another has ceased operations. The shutdowns span trading platforms, DeFi, wallets, NFTs, infrastructure, and more.
Among them, POAP’s departure feels especially poignant.
If you were around during the last crypto cycle—especially if you attended Devcon, ETHDenver, hackathons, DAO community events, or any number of online and offline meetups—there is a good chance you can still find a few POAPs in your wallet. One might have come from a major conference, another from an online talk, and another from a community event whose details you can barely remember anymore.
Most of these POAPs are worth little or nothing. But that is precisely why they may come closer to what collecting was originally about than many NFTs that once carried enormous price tags.
And that is precisely what makes POAP’s farewell so telling.
It did not collapse overnight because of a hack. There was no anonymous team disappearing with user funds, and it did not even issue a native token whose price needed to be constantly supported. It simply reached a point where even with real users, a clear use case, and strong brand recognition, it still could not find a business model capable of sustaining the project over the long term.
That is exactly the kind of shift taking place across crypto today.
In the past, we were more accustomed to discussing how a project was born. Going forward, we may need to become increasingly comfortable discussing how projects die.
And that is not necessarily a bad thing. But as everyday users, we need to understand how to avoid being caught in the aftershocks of a bear market.
1. A New Wave of Shutdowns Is Sweeping Across Web3
During crypto’s last expansion cycle, it was not particularly difficult for a project to get off the ground.
Raise funding, launch a mainnet, issue a token or run an airdrop, launch a liquidity incentive campaign—and that was often enough to attract the first wave of users. TVL, address counts, and transaction volume could rise quickly. For a surprisingly long time, whether a project actually generated revenue was not even the most urgent question.
But once the cycle turns and token prices and liquidity can no longer function as sources of funding, the model runs into a very simple question:
If no new money comes in, can the project support itself?
That is what makes the wave of project shutdowns in 2026 particularly noteworthy.
Many of the projects disappearing today are not vaporware that never had a product to begin with. They raised funding, launched, attracted real users, and in some cases were technically sound and fully operational.
Take BitMEX. On July 23, it announced that its trading platform would officially shut down on September 23, 2026.
Founded in 2014, BitMEX was once one of the defining companies in the crypto derivatives market. Perpetual swaps, 100x leverage, and a range of trading products later adopted across the industry were all closely tied to BitMEX’s early rise.
In its shutdown announcement, BitMEX even emphasized that during more than 11 years of operation, it had never lost user funds to a hack. But even that track record was not enough to turn BitMEX into a piece of infrastructure that could run indefinitely.
Similar stories have played out across DeFi and infrastructure.
Botanix, a Bitcoin L2 project nearly four years in the making, said that since launching its mainnet, the network had maintained 100% uptime with zero security incidents, processed roughly 25 million transactions, reached 200,000 wallet addresses, attracted tens of millions of dollars in assets, and integrated infrastructure and DeFi products including Chainlink and Morpho.
By traditional crypto KPIs alone, it would be difficult to call Botanix a project that “achieved nothing.” The chain was built. The product worked. Users showed up. Capital flowed in—and in meaningful amounts.
Yet Botanix ultimately decided to shut down the network. In its retrospective, the team said that organic transaction demand had failed to generate enough fee revenue to cover the long-term infrastructure costs of operating an independent network.
Crypto has spent years measuring ecosystems by TVL, address counts, and transaction volume, while rarely asking the final question:
How much real revenue are those users actually generating?
As the industry matures, projects with little genuine usage, persistently weak revenue, and ongoing maintenance costs will gradually disappear. That looks more like a structural shakeout than an industry suddenly losing its value.
In fact, once a project determines that it can no longer continue, halting new activity, publishing a clear shutdown timeline, and giving users time to migrate their assets is often far more responsible than letting development grind to a halt while pretending the project is still operating normally.
2. What Should Everyday Users Watch for During a Project’s “Slow Death”?
This brings us to an easily overlooked question.
Crypto has repeated one security principle for years:
“Not your keys, not your coins.”
As a result, many people naturally assume that once their assets are held in a wallet where they control the private keys, the most important security problem has been solved.
That principle is not wrong. But it only solves half the problem, because holding your own private keys gives you control over the account—it does not automatically guarantee that the asset itself will remain redeemable or that you will always have a viable exit path.
The reason is simple: assets displayed in the same wallet can represent fundamentally different things.
Imagine that your wallet shows $10,000 worth of assets. That balance could consist of:
- native ETH on Ethereum;
- a deposit or receipt token issued by a lending protocol;
- an LP token;
- a bridged representation of BTC issued through a cross-chain bridge.
All four appear in your wallet, and all four require your private key to authorize transfers.
But if the underlying protocol—or even the underlying network—stops operating, the outcomes can be very different.
Scenario 1: The Project Shuts Down, but Users Can Still Exit Through Smart Contracts
The wind-down of dYdX v3 is a relatively ideal example.
In 2024, dYdX decided to discontinue v3 and shift development toward the new dYdX Chain. Users were notified in advance to close their positions and withdraw USDC. After the product was shut down, the relevant contracts were frozen, while an exit mechanism remained available for users who had not yet withdrawn their funds.
This is an almost textbook example of the “walkaway test”: the team can stop providing the product, but users’ ability to withdraw their assets does not completely depend on the team remaining in business.
This is also a practical way to evaluate how truly “non-custodial” a DeFi protocol is: if the development team stopped maintaining the product tomorrow, could an ordinary user still withdraw their funds through on-chain contracts? Further reading: A Turning Point in a Decade-Long Debate: Could Ethereum Move Beyond the “Trilemma”?
Scenario 2: The Token Really Is in Your Wallet—but It Is Only a Claim on Another Asset
The story of Ren Protocol illustrates the other side of the issue.
Anyone who used DeFi during the previous cycle will probably remember Ren. It was once an important piece of BTC cross-chain infrastructure.
Users could move BTC to Ethereum through Ren and receive a wrapped token called renBTC, which they could then use as collateral in Ethereum DeFi protocols to earn yield, borrow, and more.
In theory, renBTC could sit in your own wallet. You controlled the private key, and the blockchain did indeed record your renBTC balance.
The problem was that renBTC was not BTC on the Bitcoin network.
It represented a claim on the BTC backing the Ren bridge.
So when Alameda Research collapsed in 2022 and Ren lost critical financial backing, the Ren 1.0 network began shutting down. Projects including BadgerDAO urgently warned users to unwind their renBTC exposure, because once Ren 1.0 stopped operating, holders would no longer be able to use the original bridge to redeem renBTC for native BTC on Bitcoin.
In other words, renBTC may still have been sitting in your wallet, and no one could simply burn or transfer it away. But your private key alone could not restart the Ren network after it had stopped operating and redeem that renBTC for native BTC.
The same logic applies to many bridged assets, wrapped assets, LP tokens, lending receipts, and certain staking derivatives.
What users control is the “receipt” or claim. Whether it can ultimately be redeemed for the underlying asset depends on whether the smart contracts, reserves, oracles, bridge validators, liquidity, and redemption infrastructure behind it are still functioning.
Scenario 3: If the Underlying Network Shuts Down, a Private Key Cannot Keep the Chain Producing Blocks
Go one layer deeper, and the problem becomes even more straightforward.
Some chains may shut down entirely or become effectively abandoned, making reliable block production difficult to guarantee. We have seen cases of this kind with networks such as Eclipse and AO.
If an entire network stops operating, you may still retain your private key, and historical blocks may still contain records showing how many tokens you owned.
But that does not necessarily mean you can continue transferring those assets as freely as before.
So if we break “asset control” down more fully, it contains at least three layers:
- Account control: Who controls the private key and mnemonic phrase?
- Claim on the asset: Is the asset in the wallet native, or is it a claim issued by a protocol, bridge, custodian, or asset pool?
- Ability to exit: When you actually decide to leave, do the underlying network, smart contracts, liquidity, and required infrastructure still allow the asset to be redeemed and migrated?
“Not your keys, not your coins” mainly addresses the first layer.
But when a project begins to decline, stops being maintained, or heads toward shutdown, the problems are often concentrated in the other two.
That is why, amid an ongoing structural shakeout across the industry, the more important question is:
If this project stopped operating tomorrow, would I still be able to recover my assets in full?
3. Understanding “Self-Custody” More Fully and Accurately
In reality, most projects do not suddenly go from “fully operational” one day to “completely dead” the next.
Real decline usually unfolds over a long period of time.
A practical way to spot it is to look beyond the token itself and watch four things together: people, money, code, and exit paths.
- Start with the money—especially whether genuine demand remains once liquidity incentives disappear. A higher TVL does not automatically mean greater safety, and more transactions do not necessarily mean more value. The real questions are: once token rewards are removed, how many people keep using the product? Can protocol revenue cover the cost of maintaining the team and other ongoing expenses?
- Then look at the people—especially whether social media is the only part of the project still active. Many projects will never formally announce, “We no longer have anyone developing this.” In that sense, many of the projects discussed above were relatively responsible simply for making an official announcement. A more common pattern is that GitHub sees no meaningful core code updates for six months, serious bugs remain unresolved for long periods, roadmaps are repeatedly delayed, and communities are left unattended.
- Finally, look at the exit path. This is the step everyday users are most likely to overlook—and potentially the most valuable one. For any significant on-chain asset, you should at least know which network it is on, what its contract address is, whether the balance shown in your wallet is a native asset or a receipt, how it can be redeemed for the underlying asset, and whether another way to interact with the protocol exists if the official frontend goes offline.
As the industry goes through more structural shakeouts, the meaning of “self-custody” also needs to be understood more fully.
For core assets held over the long term, keeping them in a wallet where you control the private keys remains one of the most important security fundamentals.
But once you start using DeFi, bridges, staking products, and other on-chain services, you need to ask one more question: where exactly did my assets go?
Depositing ETH into a protocol and receiving a token in your wallet does not mean that ETH is still sitting at the original address.
Bridging BTC and seeing a BTC balance on an L2 does not mean you still hold native BTC.
And moving assets into an LP position, vault, or lending market and seeing a balance on screen does not guarantee that you will be able to redeem them later at the value shown.
Closing Thoughts
POAP’s departure has struck a chord with many long-time users because it once again reminds those still in Web3 of a simple reality:
A product can have no token, no elaborate financial game, and a community that genuinely loves it—and still eventually reach the end of its life.
That is not an anomaly unique to blockchain.
Quite the opposite. It may be a sign that crypto is finally starting to look more like a normal industry:
Products have life cycles. Teams change. Failed business models disappear. And limited developer resources, capital, and user attention continue flowing toward more productive parts of the market.
We will probably see many more farewells like these in the years ahead.
Some projects, like POAP, will leave behind on-chain memories from a particular era.
Some protocols, like dYdX v3, will wind down in an orderly way while allowing users to continue exiting through smart contracts.
And some assets, like renBTC, will remind people—only when the infrastructure behind them is about to disappear—to ask what exactly they have been holding in their wallets all along.
Protocols can disappear. Projects can fail. Even an entire blockchain can eventually reach the end of its life.
But the most important underlying principle of crypto asset security should remain unchanged:
Do not make your ultimate control over your assets dependent on the assumption that any single project will stay in business forever.
It is a reminder worth keeping in mind.