Three Reports Give Conflicting Numbers and None Has a Document to Settle Which Is Right

Across an exchange hack, a token rally and an on-chain read, published accounts disagree on a date, a price and a ratio, and no primary source exists yet to referee any of them.

Across an exchange hack, a token rally and an on-chain read, published accounts disagree on a date, a price and a ratio, and no primary source exists yet to referee any of them.

A Hacked Account's Timeline Depends on Who You Read

When crypto.news and Crypto Economy both wrote up the MEXC $340,000 withdrawal incident, they told two different stories about the one detail that matters most in an intrusion case: the moment the attacker's API key came into existence. The two outlets covering the story do not agree on the date and time the key was created, which means the same incident currently has two competing chronologies in public circulation. Neither report is a leaked internal log or an MEXC statement fixing the timestamp, so there is no primary document available to referee the difference. Until MEXC itself, or a forensic disclosure, names an authoritative time, both versions have to be treated as unconfirmed rather than one being dismissed as wrong.

LINK's Rally Is Reported With No Two Publishers Agreeing on Its Size

CoinJournal and CoinGape both covered LINK's reaction to the CCIP 2.0 launch, and both frame it as a genuine market move, but they hand readers different figures for the size of the price gain and for how far trading volume rose. That is not a case of one outlet rounding and the other not; the two figures diverge enough that a reader cannot simply average them into one number. With two independent publishers involved rather than one, carried by two feeds, the story clears the newsroom's usual bar for corroboration that something happened. It does not clear the separate bar of agreeing on how much happened, and the CCIP 2.0 launch being the trigger is the only part of the account that both sides confirm.

Long-Term Holder Data Splits Into Two Bitcoin Prices

CryptoBriefing and Coinfomania both drew on CryptoQuant data to report that Bitcoin's long-term holders are exiting a period of shallow stress, which is itself a specific and checkable claim about on-chain positioning. But the two write-ups quote different Bitcoin prices for the same window, and they do not even agree on the more basic point of whether the MVRV ratio fell below 1.0. That distinction is not cosmetic: MVRV below 1.0 means the average long-term holder is sitting on an unrealised loss, and MVRV above 1.0 means the opposite. Whether the underlying holder base was under pressure or was not rests entirely on which of the two accounts is correct, and nothing in either report resolves that.

None of These Splits Has a Document to Settle It

Set side by side, the hack, the token rally and the on-chain read share one feature: in each case both outlets are working from the same underlying event or dataset, yet they produce numbers that cannot both be true at once. That is different from a single-source claim waiting on confirmation; here confirmation exists, but it disagrees with itself. None of the four reports is a primary filing, an exchange statement or a raw CryptoQuant export that a reader could check directly, so this edition adjudicates none of them. The MEXC timeline is the one to hold onto, because a wrong timestamp on an intrusion has operational consequences beyond a rounding error, and it is the discrepancy most likely to be closed by an actual disclosure rather than a second opinion.

Two publishers agreeing that something happened is not the same as two publishers agreeing on what happened, and until a primary source appears for the MEXC timeline, the LINK move or the MVRV read, all three should be cited with their disagreement attached.

Stories in this edition

Publisher counts are as at publication and keep moving; each story page carries the live number.

• MEXC Hack Reports Disagree on Date API Key Was Created 1 independent publisher — reports two different timestamps for the API key with no primary log to settle which is right
• Chainlink Reports Disagree on LINK's Price Gain, Volume Surge 2 independent publishers — corroborated that LINK reacted to CCIP 2.0 but not on the scale of the reaction
• Bitcoin Price, MVRV Level Disputed in LTH Reports 1 independent publisher — disputes both the Bitcoin price and whether MVRV crossed below 1.0 in the same CryptoQuant-sourced dataset

Two publishers agreeing that something happened is not the same as two publishers agreeing on what happened, and until a primary source appears for the MEXC timeline, the LINK move or the MVRV read, all three should be cited with their disagreement attached.