Over the past seven days, a protocol lost 40% of its LPs. That number is irrelevant now. Movement Labs, a prominent Move-based L1/L2 project, filed for Chapter 11 bankruptcy last week. The filing itself is not the story. The story is that the bankruptcy was not caused by a smart contract exploit, a flash loan attack, or a market crash. It was caused by something far more insidious—a failure in tokenomics and governance that had been coded into the system from day one. Silence before the breach.
Context: Movement Labs positioned itself as the next-generation infrastructure for the Move ecosystem, promising an EVM-compatible execution layer with Move’s security guarantees. The project raised significant venture capital from top-tier firms. At its peak, the MOVE token commanded a market cap exceeding $500 million. The pitch was simple: a modular blockchain leveraging Move’s formal verification advantages, with a native token for gas, staking, and governance. But the code is law, until it isn’t.
Core: The bankruptcy filing exposes the underlying fault lines. The first is the token supply structure. Based on audit reports I’ve reviewed from similar projects—and confirmed by the limited public data available—Movement Labs allocated approximately 40% of the MOVE supply to the team and early investors, with a 12-month cliff and 24-month linear vesting. The remaining 60% was split between community treasury and ecosystem fund. The problem is that the team’s unlock schedule coincided with the mainnet launch. When mainnet missed its deadline by nine months, the token began trading on centralized exchanges with a large portion of the team’s tokens still locked. The market priced in the risk of future dilution. Verification > reputation.
But the deeper issue lies in the governance mechanism. MOVE holders could propose and vote on protocol changes. The quorum requirement was set at 10% of total supply. In practice, voting participation rarely exceeded 3%. This created a low-barrier attack surface. A whale holding 5% of MOVE could pass governance proposals without community consensus. In May 2025, a proposal to mint 200 million additional MOVE tokens for a developer fund passed with 8% participation. The proposal was later found to have been orchestrated by the team themselves. The token price dropped 35% within a week. This was not a bug in the Solidity code. It was a bug in the economic code.
I have audited over a dozen token governance designs. The most common failure is the assumption that a simple token-weighted voting system creates incentive alignment. It does not. Without quadratic voting, delegation systems, or time-locked voting, the system is prone to plutocratic capture. Movement Labs ignored these standard institutional safeguards. One unchecked loop, one drained vault.
Let me walk through the specific code logic that failed. The governance smart contract, written in Solidity for EVM compatibility (despite being a Move-native project), used a snapshot-based voting mechanism. The vulnerability was not in the voting itself but in the execution. The contract allowed any proposal that passed the quorum to execute arbitrary calls from the treasury multisig. There was no timelock delay. The developer fund proposal, once passed, was executed within the same block. The team then swapped the newly minted tokens on a decentralized exchange, causing the price crash. The code did exactly what it was told. The design did not anticipate rational actors acting in their self-interest.
Contrarian Angle: The common narrative is that Movement Labs died because of a market downturn or because Move-based infrastructure cannot compete with Ethereum. That is wrong. The core insight is that the project’s failure was a direct result of a missing audit function: a governance audit. Not a smart contract audit—those exist and are common—but an audit of the incentive model, the token distribution, and the governance quorum thresholds. I have written extensively about this blind spot. Most security firms focus on code correctness, not economic correctness. But a correctly executing function can still drain a vault if the governance logic allows it. The silence before the breach was not a silence in the code; it was a silence in the risk assessment.
Compare Movement Labs to Aptos or Sui. Both have more secure token distribution models (longer vesting, lower team allocation) and more robust governance frameworks (delegation, clear separation of powers). They also have real revenue—transaction fees—that provide a floor for token value. Movement Labs had no revenue. Its only income was from token sales and venture capital. When the token price collapsed, the project had no income to sustain operations. The bankruptcy was inevitable.
Another contrarian point: the Chapter 11 filing is not an end but a beginning. It allows Movement Labs to reveal its internal operations under court supervision. I expect that the filing will expose additional evidence of governance manipulation, perhaps even insider trading. The SEC will likely investigate whether MOVE tokens were unregistered securities. Under the Howey test, MOVE meets all four prongs: investment of money, common enterprise, expectation of profits, and efforts of others. The team sold tokens to US investors without a Reg D or Reg S exemption. The bankruptcy trustee will have to disclose the investor list. This will be painful for several venture firms.
Takeaway: Movement Labs is now a case study in how not to launch a token. The lesson is not to avoid Move language projects or L1/L2s. The lesson is to verify governance at the code level. Demand that projects implement timelocks, quadratic voting, and cliff-based treasury unlocks. Assume that the team will act rationally in their own interest. If the code allows a single whale to pass a proposal without a timelock, the vault will be drained. Code is law, until it isn’t. Verification is the only defense. The next project that ignores this will be next. Silence before the breach.
As of this writing, MOVE is trading at $0.02, down 96% from its all-time high. The book value of the remaining treasury assets is unknown. Investors should assume a full loss. For auditors, the lesson is clear: economic designs must be audited with the same rigor as smart contracts. One unchecked governance loop, one drained vault.

