The data shows it.
Rushikesh Manche, co-founder of Movement Labs, filed a notice last week seeking $1.7 million from the bankrupt estate. The sum is for legal fees accrued during a federal grand jury investigation into the MOVE token issuance. This is not a routine creditor claim. This is a surgical strike aimed at the heart of the project’s failure.
The court in Delaware granted the request. Manche retains his equity, a ghost in the machine of a company he helped build but was subsequently expelled from. The company now called Movement Labs (MVMT) sits in Chapter 11, its assets frozen, its token price circling zero.
Code does not lie, but it does leave traces. The trace here is not a reentrancy bug or a flawed smart contract. It is a trail of broken promises, failed governance, and a classic, avoidable destruction of value.
Context: The Rise and Fall of a Narrative
Movement Labs was the embodiment of a compelling thesis: bring the Move language—originally developed by Facebook for the Diem project—to Ethereum as a Layer 2. The tech was interesting. Move, with its formal verification capabilities and resource-oriented programming model, offered a counter-narrative to Solidity’s fragility. In early 2024, this was enough. Polychain Capital led a funding round, placing a bet on a team that promised to bridge the security of Move with the liquidity of Ethereum.
The network, Movement Network, launched its testnet. The community grew. The narrative was simple: efficient, secure, and new. Then came the token.
The MOVE token was issued in December 2024 with high fanfare and a high fully-diluted valuation (FDV). It was a classic “low float, high FDV” launch, a model that by late 2024 was already showing cracks in other projects. But the real problem was not the tokenomics on paper. It was the execution.
According to court documents and internal sources, the market maker responsible for stabilizing the token began to sell their allocated tokens into the market shortly after the launch. The price collapsed. The team panicked. An internal investigation was launched. The target of the investigation was the co-founder, Rushikesh Manche.
Core: The Engineering of a Disaster
Let us strip away the narrative. This is not a story of a bad market or a hack. This is a story of a system—a governance system—that failed a stress test that it should have passed.
First, the token issuance. The MOVE token was not an autonomous agent; it was a tool controlled by humans. The structure of the market maker agreement, the lack of on-chain verification for the token’s supply, and the absence of a transparent vesting schedule created a single point of failure: the trust in the founding team.
The market maker was not the problem. The inability of the system to verify the market maker’s actions was the problem.
The investigation into Manche suggests that he may have authorized or been complicit in the market maker’s actions. The legal filing by Manche for $1.7 million in fees to defend against a federal grand jury probe confirms that the US Department of Justice is now interested. This moves the failure from a commercial dispute to a potential criminal issue.
Second, the governance collapse. The removal of Manche from the company was not a clean, transparent process. It was a battle. He was ousted, yet he retained his shares. He became the largest unsecured creditor of the very company he co-founded. This is not a governance model; it is a political hostage situation.
In the red, we find the structural truth. The structure was flawed from the start. The team did not have a clear separation of powers. The founders controlled the token, the treasury, and the code. When a founder was suspected of wrongdoing, the only tool the remaining team had was a legal axe: expulsion. There was no smart contract-based vesting schedule that could be triggered. There was no DAO to vote on the issue. There was only a corporate boardroom and a bankruptcy filing.
Third, the technical mitigation. The core development team did not stop working. They spun out a new entity called “Move Industries.” This is the critical, often-missed detail. The technology is not dead. It has just changed hands. The intellectual property and the developer talent have moved to a new shell, leaving the old MVP entity to rot in bankruptcy court.
This is a standard corporate maneuver, but it reveals a deep truth about the crypto industry: the code is not the company. The network is not the token. The developers can abandon the brand and the debt, leaving the token holders holding the bag.
Contrarian: The Technology Was the Only Survivor
The surface-level narrative is that Movement Labs died. The tokens are worthless. The brand is toxic. The bearish take is that this is a final nail in the coffin for Move language L2s.
The contrarian view, supported by the data, is that the technology itself is now in a healthier position. The old entity, MVP, was burdened by a toxic capital structure, a ruined reputation, and a looming DOJ investigation. By walling off that liability into a Chapter 11 case, the remaining developers have essentially performed a “bad bank” spin-off.
Move Industries can now start fresh. It has no debt to Unsecured creditors (except Manche’s legal fees, which are now a claim against the old estate, not the new entity). It can re-brand, re-tokenize (with a new, better tokenomics model), and re-enter the market. The tech stack is intact. The developer community is still there.
The real tragedy is not the death of the technology, but the destruction of the trust that was attached to the MOVE token. This event will be a case study on why you should not conflate the speculative value of a token with the intrinsic value of the underlying technology. The two can be separated, violently.
Takeaway: We Build Frameworks, Not Just Tokens
The Movement Labs saga is a textbook example of decentralized system failure caused by centralized human nature. The failure was not in the code; it was in the governance. The founders lacked a protocol for their own conflict. The market maker lacked a verifiable commitment. The token lacked a built-in circuit breaker.
The lesson is not to avoid Move language L2s. The lesson is to audit the governance framework as rigorously as you audit the smart contracts. Ask the hard questions: What happens when a founder is suspected of fraud? Who controls the market maker keys? How is a treasury re-allocated in a emergency? If the answer is “the founding team will decide,” then the project is a centralized application wearing a Layer 2 disguise.
Yield is a symptom, not the cure. And in this case, the symptom was a token that promised a yield on future speculation, only to deliver a yield of zero after a governance meltdown.
The grand jury investigation is the final chapter for MVP. But for Move Industries, it is the first page of a new, and hopefully cleaner, story. The code is still there. The question is whether the new builders can learn from the ghost in the machine.