Digital Assets
Serum (SRM): Upgrade-Key Risk After FTX
Serum’s breakdown after FTX shows how centralized upgrade authority can undermine decentralized market infrastructure.

Serum (SRM ) was an order-book exchange infrastructure project on Solana (SOL ). Its failure became a clear example of a risk that is easy to overlook in DeFi: an application can run on a public blockchain while a small number of people retain decisive control over its software.
The dependency exposed by FTX
After FTX collapsed in November 2022, the security of Serum’s upgrade authority became a concern. The OpenBook project’s account of its origins explains why the community forked Serum and placed upgrade control under a different multisignature arrangement.
A fork can preserve useful code and give applications another place to operate. It does not automatically preserve the economics of the original token. SRM holders should not infer ownership of OpenBook, a conversion entitlement or a claim on a successor’s activity from the fact that the successor used Serum’s code.
What happened to the original investment thesis
A Kraken cryptoasset statement for SRM describes the original mainnet as defunct and highlights very limited liquidity and uncertainty about the token’s role. Those conditions make older descriptions of an expanding Serum ecosystem unsuitable as an explanation of the asset a reader might encounter today.
An exchange listing, a surviving token contract or a quoted price can outlast the project’s original purpose. None establishes that meaningful market depth, development support or the former utility has returned.
The lesson: inspect control as well as code
Upgrade authority determines who can change an application after users have committed funds or built products around it. A technically open system can therefore have a concentrated operational dependency. The quality of its controls matters alongside transaction speed and fees.
Serum also separates the survival of technology from the survival of a token thesis. Developers can reuse software while leaving a token behind. Following the users and the operating infrastructure is more informative than assuming that code reuse will pass value to every legacy holder.












