Uniswap Wins Legal Case Against Scam Lawsuit, Affirms Open-Source DeFi Liability Protection

iconCryptofrontnews
Share
Share IconShare IconShare IconShare IconShare IconShare IconCopy
AI summary iconSummary

expand icon
Uniswap Labs and Hayden Adams won a four-year lawsuit in Manhattan, dismissing claims of liability for scam tokens. The court ruled the platform cannot be held responsible for third-party actions, noting open-source DeFi code does not create legal liability. The ruling supports CFT efforts by reinforcing that DeFi platforms are not inherently complicit in fraudulent activity. As liquidity and crypto markets expand, future scrutiny may target areas like token curation and fee capture.
  • Uniswap wins four-year lawsuit, confirming open-source DeFi code alone doesn’t create legal liability.
  • Courts distinguish toolmaking from operating a service; scammers, not developers, bear fraud responsibility.
  • Future scrutiny may focus on front ends, token curation, and fee capture—where human control exists.

Uniswap Labs and founder Hayden Adams scored a major legal win in Manhattan, ending a four-year class action lawsuit. The case targeted the decentralized exchange for scam cryptocurrencies traded on its platform.

Judge Katherine Polk Failla dismissed the suit with prejudice on Monday, ruling that the plaintiffs could not hold Uniswap liable for the actions of unknown third-party token issuers.

The lawsuit, led by Nessa Risley, initially named Uniswap, Adams, and venture firms Paradigm, Andreessen Horowitz, and Union Square Ventures in April 2022. After an initial dismissal in August 2023, the plaintiffs revised their complaint to focus on alleged state-level consumer protection violations.

They claimed Uniswap allowed “rug pulls and pump-and-dump schemes” to occur. However, Judge Polk Failla wrote, “merely creating an environment where fraud could exist is not the same as affirmatively assisting in its perpetration.”

Open-Source Software Shield Strengthened

Hayden Adams celebrated the outcome on X, saying it sets a “good, sensible outcome” and a new legal precedent. He emphasized, “If you write open source smart contract code, and the code is used by scammers, the scammers are liable, not the open source devs.”

The court agreed, noting that plaintiffs failed to prove Uniswap had knowledge of the fraud or substantially assisted in its commission. Consequently, the case reinforces that publishing general-purpose DeFi code does not automatically equate to liability.

Moreover, the ruling draws a clear distinction between DeFi platforms and crypto mixers. While DeFi cases hinge on toolmaking versus operational control, mixer cases often involve criminal charges like money laundering or sanctions violations.

The Department of Justice has highlighted these distinctions in cases like Tornado Cash and Roman Storm, focusing on active service operation rather than mere code authorship.

Operational Chokepoints Under Scrutiny

Going forward, legal attention may shift to areas where human control intersects with operations. Front ends, token curation, fee capture, and marketing channels now attract greater regulatory and civil scrutiny. DeFi projects can strengthen their defense by maintaining a clear “infrastructure only” stance.

Uniswap’s win confirms that providing decentralized tools alone does not create legal liability, but any operational control over transactions could change the calculus.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.