CFTC v. Jimmy Gale Watson (pump and dump, 2022)

Judgment entered

✓ Checked against the primary document on October 2, 2026. The library's summary, tags and figures for this record were compared with the regulator's own document by an AI model (Claude) following written instructions, with sampled and disputed records read a second time. No lawyer has reviewed them. A checked record can still contain errors, and checked does not mean endorsed. See how we check records or report a correction.

Report an error in this record (cftc-jimmy-gale-watson-pump-and-dump-2022) by email

In 2022 the Commodity Futures Trading Commission announced a July 14 consent order in the Southern District of New York resolving its digital-asset pump-and-dump case against Jimmy Gale Watson of Dallas. The release says he must disgorge over $146,000 and pay an equal civil monetary penalty, and it imposes trading and registration bans.

The record

What was ordered

Civil penalty

$146k

Disgorgement

$146k

Prejudgment interest

—

Total relief

$292k

Alleged gain

—

A dash means the release did not state a figure we could extract, not that the figure is zero. Penalty and disgorgement are stored separately so aggregates across the library do not double-count the same dollars.

What is alleged to have happened

the Commodity Futures Trading Commission announced this matter on July 18, 2022 as release 8558-22. The respondents named are Jimmy Gale Watson (1 individual, 0 entities).

The release states that, as found in the order, Watson helped pick digital assets, secretly built positions in them, and sold into the demand created by misleading social-media endorsements from his co-defendant John McAfee. The same release describes his order as resolving the claims in the March 2021 CFTC action. This library tags the matter as pump and dump.

The conduct is recorded against crypto.

The relief recorded in our data is disgorgement of about $146,000 and an equal civil monetary penalty of about $146,000, each described in the release as over $146,000. Penalty and disgorgement are distinct: disgorgement returns the gain, while the penalty is punitive. We store them separately so that aggregate figures across the library are not double-counted.

Non-monetary relief recorded: trading ban.

The release references a parallel criminal proceeding. Where a criminal case exists, the civil and criminal outcomes are recorded separately, because they resolve on different standards of proof.

For the regulator's own account of the facts, read the primary document linked above. This page deliberately summarises the structured record rather than reproducing the release.

What technique is this, and how does it work?

This action is tagged with one technique in our taxonomy. The tagging is ours: regulators charge statutory provisions, not technique names, so the mapping is an editorial judgement described in our editorial policy.

• Pump and dump — see how it works, what statute it engages, and every other action tagged the same way.

Timeline

1. 2022-07-18 CFTC release published

Primary documents

Everything on this page derives from the documents below. Where our summary and the primary document disagree, the primary document is right.

• CFTC release
• CFTC order or complaint

The linked release is a work of the United States government and is not subject to copyright. Our summary and narrative above are our own writing.

Same matter

The library links these 2 records because they appear to concern one matter: the same lead defendant, an overlapping technique tag and close filing dates, or a shared court docket or a release that cites the other. Records are listed by date filed.

This grouping is the library's, made by matching names, techniques, dates and citations when the site is built. It is not the regulator's or a court's determination that the records are one case, and it errs towards missing a link rather than making a false one.

Related actions

Other actions in the library sharing at least one technique tag with this one.

Record added September 20, 2026. submit a correction.