The JACK memecoin crash is one story. The category snapshots are two.

The JACK memecoin crash, on September 29, 2026, is a case of a huge percentage move printed on a very small liquidity figure. The Currency Analytics describes the day as a memecoin market cap of about $35.4 billion, down 3.7% on the day, with JACK losing 86% in about six hours while about $12.8 million traded on about $54,000 of liquidity. A second account, U.Today via CryptoNews at 04:49 UTC, does not hand you the same category picture.

TL;DR - The Currency Analytics, for September 29: category about $35.4 billion, down 3.7% on the day. JACK down 86% in about six hours, about $54,000 of liquidity, about $12.8 million traded. - On JACK memecoin crash, U.Today via CryptoNews: category down about 4% on the day, plus a September 28 snapshot near $35.2 billion that was down 4.2% on that prior day. JACK down 86% in six hours after $12.8 million in volume against $54,000 of liquidity. - The JACK shape matches. The category numbers do not. Do not average them into one market-cap print.

What actually happened

Keep the snapshots apart. Nothing here is a suggestion to buy, sell, or expect a bounce.

Start with the category, because that is where the outlets refuse to be one chart. The Currency Analytics ties September 29 to a memecoin market cap of about $35.4 billion and a 3.7% decline on that day. U.Today, via CryptoNews, says the category was down about 4% on the day, and it parks a different picture on September 28: near $35.2 billion, down 4.2% on that prior day.

About 3.7% and about 4% are not the same day-move even before you notice the levels. About $35.4 billion on the 29th and near $35.2 billion on the 28th are different dates. They disagree as snapshots. Smoothing them into "around $35 billion, down about 4%" throws away the only precision the pages gave you.

The JACK lines are closer, and they still deserve both wordings. The Currency Analytics says JACK lost 86% in about six hours on about $54,000 of liquidity while about $12.8 million traded. U.Today via CryptoNews says JACK fell 86% in six hours after $12.8 million in volume against $54,000 of liquidity.

The percentage, the six-hour window, the volume figure, and the liquidity figure show up in both. One outlet sprinkles "about," and the prepositions differ: on that liquidity while that amount traded, versus after that volume against that liquidity. Show both. Do not invent a third sentence that pretends the wording was identical.

What the pair does make obvious, without any new arithmetic, is the mismatch in scale. A liquidity figure around $54,000 sits next to a volume figure around $12.8 million in both stories. Volume is not liquidity.

On JACK memecoin crash, one is what traded. The other is the pool those stories say was there. When the traded number dwarfs the pool number, a large percentage move is not a mystery that needs a secret catalyst to be legible.

The pages already printed the awkward pair of figures. This article will not divide them into a fresh multiple. The pack did not publish that multiple, and a homemade one would only look more official than it is.

The time stamps are part of not smearing the day. The Currency Analytics is a September 29 story. The U.Today piece via CryptoNews carries 04:49 UTC on September 29, and it explicitly reaches back to a September 28 category snapshot.

A morning UTC story that cites yesterday's level plus today's rough percent is not the same object as a same-day level of about $35.4 billion. If you cite "the" memecoin market cap from this pack, you are already wrong, because the pack has two.

No other ticker's buyback, treasury, or rescue story belongs in this telling. Those figures are not part of the JACK account used here. Adding them would change the subject and pretend a different market mechanism explained an 86% print. The mechanism on the page is the thin liquidity figure beside the larger volume figure, inside a category day that the two outlets do not score identically.

What to do as a reader

On JACK memecoin crash, pin each number to its outlet and its date before you repeat it. If you say $35.4 billion and down 3.7%, you are quoting The Currency Analytics for September 29, and you owe the "about." If you say near $35.2 billion and down 4.2%, you are quoting the September 28 snapshot in the U.Today via CryptoNews piece, not the 29th. If you say the category was down about 4% on the day, that is the same second outlet's line for the day, and it is not a correction of the 3.7% line.

They disagree. The honest slide has two rows.

Use the same discipline on JACK. "86% in about six hours" plus "about $54,000" plus "about $12.8 million" is The Currency Analytics. "86% in six hours" plus "$12.8 million in volume against $54,000 of liquidity" is U.Today via CryptoNews.

The story is the same shape. The hedges are not the same. Dropping every "about" makes the first outlet sound more precise than it was. Adding "about" to the second makes it sound softer than it was.

Read the liquidity line as a warning about how prints happen, not as a setup. A pool that small, next to volume in the millions, can gap because there is not much book underneath the print. That is a description of the figures they published.

It is not a forecast that the move continues, reverses, or "should" do anything. Memecoin percentages are very good at looking like a plan if you let them. They are not a plan. This article does not have a side, an entry, or a target, and it will not grow one.

On JACK memecoin crash, if you track the category for context, track the disagreement too. A 3.7% down day and an about-4% down day can sit beside a token that fell 86% without either category number "explaining" JACK. The category is the backdrop each outlet chose.

JACK is the outlier both of them stopped on. Do not let the backdrop's smaller percent make the token move look measured, and do not let the token move rewrite the backdrop into a crash of the whole category. The pages did not say the category fell 86%. They said JACK did.

A practical habit for the next thin-book headline: write volume and liquidity on separate lines, copy the "about" if it is there, and refuse to publish a ratio you calculated in the margin. Then ask which day's category snapshot you are even looking at. If you cannot answer, you are not ready to quote the market cap.

The work is clerical. Clerical is what keeps a viral percentage from eating the sentence next to it.

What this does not decide

It does not decide whether either data vendor's market-cap method is right. The Currency Analytics and the CryptoNews relay of U.Today simply disagree at the snapshot level, and the pack does not include a methodology appendix. You can notice the conflict without crowning a winner. Crowning one would be an extra fact.

It does not decide who traded the $12.8 million, whether the liquidity figure was the whole pool or a venue's slice, or what JACK is besides the name in these headlines. Those details are not in the pack. Filling them with a project biography would be fan fiction stapled to a market blurb. The blurb is enough work on its own.

It does not decide what anyone should hold. An 86% decline is a reported move, not a moral and not an opportunity. Thin liquidity explains how a tape can travel that far in about six hours.

It does not tell you the next six hours. If a post adds a promise, a target, or a second token's buyback math, it has left the source pack.

On JACK memecoin crash, the two accounts are The Currency Analytics and U.Today via CryptoNews. Quote them side by side. Do not average the category. Do not trade off the recap.

Readers who want sourced recaps that are already on the site can read DogeOS public testnet and PUMP token buyback burn as separate live posts.