Why Jonathan Teplitsky Chose to Participate in the Dapper Labs Class Action

Plaintiff · Proposed Class Representative · Flow Token Class Action Lawsuit

Why I Chose to Participate in This Case

I chose to participate in this case because people who bought and held Flow Tokens deserved the truth.

Flow was marketed as a decentralized blockchain. Dapper Labs and the Flow Foundation told the public that Flow was open, decentralized, and controlled by the community. That mattered because decentralization is not a side feature of blockchain. It is the core promise. People trust a blockchain because they believe they are relying on rules, transparency, and cryptography — not the discretion of a small group of insiders.

But when Flow was tested, that promise broke.

The Flow Blockchain Security Incident

In December 2025, the Flow blockchain suffered a security incident. An attacker exploited the network, minted fraudulent tokens, transferred them across numerous Flow accounts, and extracted approximately $3.9 million from the network. More than 1,000 accounts were contaminated in some way.

What happened next revealed the real issue.

Centralized Control Over a “Decentralized” Network

First, the Flow Foundation announced that the network would be restored to a checkpoint before the exploit. In plain English, Flow would roll back the blockchain and erase transaction history. That decision struck at one of the core principles of blockchain: immutability.

After public backlash, the plan changed. The revised plan gave a privileged service account temporary administrative powers to enter affected accounts and destroy counterfeit tokens. That meant the system could be altered through a centralized administrative mechanism.

That is the heart of this case.

Accountability for Decentralization Claims

If a blockchain can be paused, rolled back, or altered through decisions made by a concentrated core team, then users are not simply trusting code. They are trusting the people who control the system. That is not the same thing as the decentralized, community-controlled network that was promoted to the public.

This case is not an attack on blockchain. I believe in blockchain. But blockchain only works when the public can trust that a network is what it claims to be. If a company builds value by telling users that its network is decentralized, open, and community-controlled, then it should be held accountable when that claim does not match reality.

The Damage to Flow Token Holders

The damage was not theoretical.

After the rollback announcement and the governance crisis that followed, the price of Flow Token fell more than 40%. The market capitalization of Flow lost more than $100 million within hours, and losses later surpassed $400 million. The loss of trust was not just about the hack itself. It was about governance, control, and whether Flow was actually decentralized in the way people had been led to believe.

The people hurt by this were not just institutions or insiders. Many were ordinary token holders and retail investors. They bought into an ecosystem that was promoted as decentralized and community-controlled. They did not know that meaningful control over the blockchain was concentrated in the hands of a small core team.

Why This Class Action Matters

This is a David-and-Goliath situation: a large blockchain company and its related foundation on one side, and thousands of token holders on the other. Most people harmed by this would never be able to take on that fight alone. A class action gives them a way to be heard together.

I chose to participate in this case because someone had to stand up for those people.

A Case About Accountability

At bottom, this case is about accountability. If a company benefits from the language of decentralization, it should have to live by the substance of decentralization. And if people were misled into trusting a system that was not what it claimed to be, they deserve a fair process, a full accounting, and a chance to recover what they lost.