Skip to main content

Public — correction log, archive

Corrections CC-2026-0001 to CC-2026-0020

Factual errors, misapplied scoring, stale data and claims the site could not back. Each entry says what was wrong, what was fixed, how it was caught and whether the published order moved. An entry whose logged date is later than its corrected date was copied here from the methodology or data changelog that first published the fix. No entry is ever deleted.

This page prints the corrections numbered CC-2026-0001 to CC-2026-0020, in full. It is closed: no entry is added to it or taken from it. 20 corrections, logged 2026-09-14. All archive pages ·

IDCC-2026-0020Corrected2026-09-14TypescoringSeverityhigh
Provider: Binance
What was wrong

/api/agent-query, /assistant and /api/v1/recommend ranked from typed card fees, spreads, APRs and twelve typed security scores, and returned Binance as #1 for Germany, where the engine excludes Binance.

What was fixed

The pick is the #1 of rankings.json for the category the question maps to; a stated country removes only rows the engine excludes, and responses state no fee, spread or security score.

How it was caught

The comparison audit behind docs/path-to-ten.md, programme W1-16.

Did the published order move?

Not on chainchoice.io: no published or wizard order changed. The API now returns the published order (exchange: binance to bybit_exchange in its fixtures).

Recorded in: methodology 2026.09.11
IDCC-2026-0019Corrected2026-09-14TypescoringSeveritymaterial
Categories: Bug Bounty Platforms, Tokenised Carbon Credits, Cross-Chain Messaging, Flash Loan Venues, Blockchain Indexers, Institutional Custody, Layer-1 Blockchains, Perp House Vaults, Prediction Markets, Shared Sequencers, Simple Buy, Smart Accounts & Multisig, Stablecoin Settlement, Stablecoin Yield, Tax Software, Token Launch Platforms, Tokenised Commodities
What was wrong

Find My Best called a lead "decisive" or "strong" when the top two printed the same score, or when the #1 was one move from losing first place in the published robustness sweep.

What was fixed

Such leads are capped at "moderate", and the results page reads "How close was this call?" from the recomputed sweep instead of a linear estimate.

How it was caught

The comparison audit behind docs/path-to-ten.md, programme W1-05.

Did the published order move?

No. No order, score or eligibility changed; 59 personalised cases changed their confidence label.

Recorded in: methodology 2026.09.11
IDCC-2026-0018Corrected2026-09-13Logged2026-09-14Typestale dataSeverityhigh
Categories: DEXs, Perp DEXs, DEX Aggregators · Providers: Drift, Odos, Vertex, Synthetix Perps, Matcha, CowSwap, GMX, Hyperliquid, Jupiter Perps, Curve
What was wrong

Drift (paused since 1 April 2026) and Odos (shut down 27 July 2026) were still ranked, the Synthetix Perps record described the retired debt-pool product, and 69 structural facts across dex, perp_dex and dex_aggregator no longer matched their sources.

What was fixed

Each scored fact was re-read from the protocol’s own docs, terms, audit pages, on-chain calls or DefiLlama, and only verified values were applied.

How it was caught

The 36 rows were past the 45-day review cadence; an adversarial model run re-fetched every source.

Did the published order move?

Yes. dex_aggregator’s #1 changed from CowSwap to Matcha; Synthetix Perps and Drift fell to the floor of perp_dex (Hyperliquid 70 to 62, GMX 65 to 60, Jupiter Perps 67 to 60); Curve fell 54 to 49 in dex.

Recorded in: methodology 2026.09.10
IDCC-2026-0017Corrected2026-09-13Logged2026-09-14TypefactualSeveritymaterial
Categories: Perp DEXs, Perp House Vaults · Providers: Gains Network (gTrade), GMX, GMX GM pools, Jupiter Perps, Helix, Paradex, Lighter, Hyperliquid
What was wrong

Seven perp venues and GMX’s GM pools were shown as available to US readers, and some to Canadian and UK readers, although each venue’s own terms restrict those markets.

What was fixed

Each record quotes its terms page with the date the page states, names the restricted countries this site can match and drops the US tag.

How it was caught

The follow-up to audit finding G-10 (methodology 2026.09.8): each venue’s terms were rendered and read on 2026-09-13.

Did the published order move?

No. The published ranking is unchanged in all 119 categories; one golden case changed its winner (perp_house_vaults for a US reader).

Recorded in: methodology 2026.09.9
IDCC-2026-0016Corrected2026-09-13Logged2026-09-14TypefactualSeveritymaterial
Category: Perp DEXs · Provider: dYdX
What was wrong

dYdX was shown as available to readers in the United States and the United Kingdom, while dYdX’s help centre lists the United States, Canada and the United Kingdom as restricted jurisdictions.

What was fixed

The record quotes that page, names those three markets as restricted and drops the US tag.

How it was caught

Audit finding G-10; no golden case covered a US or UK perp_dex reader (commit 9f8ac682).

Did the published order move?

No. The published ranking is unchanged in all 119 categories; personalised perp_dex runs for US, UK and Canadian readers no longer rank dYdX.

Recorded in: methodology 2026.09.8
IDCC-2026-0015Corrected2026-09-13Logged2026-09-14TypefactualSeveritymaterial
Category: L2 Blockchains · Providers: Blast, Manta Pacific
What was wrong

Blast and Manta Pacific were recorded as optimistic rollups; L2BEAT lists both under "Other" with State Validation "None", so the fraud-proof guarantee "optimistic" implies does not exist.

What was fixed

Both carry rollupType no_proof_system, with taglines, descriptions and pricing notes rewritten to L2BEAT’s classification.

How it was caught

check-review-cadence-is-kept failed on 2026-09-13 because l2_chains evidence had crossed the 45-day cadence, and the re-read against L2BEAT disagreed on these two.

Did the published order move?

No. rankings.json is unchanged in every category; one personalised case moved (Blast 72 to 69, still 8th).

Recorded in: methodology 2026.09.7
IDCC-2026-0014Corrected2026-09-11Logged2026-09-14TypescoringSeveritymaterial
Categories: Bridges, Trading Bots
What was wrong

The tie-break gave a row an extra point for "strong evidence confidence", a value derived from the availability score, so availability decided a tie it had already been weighed into, under a name that said evidence.

What was fixed

The factor was removed; the tie-break no longer reads availability.

How it was caught

An internal audit of the tie-break (commit 547c953f); the changelog entry does not record it.

Did the published order move?

No. 0 of 119 categories changed published order or any score; personalised runs in bridges and trading_bots reordered rows already tied on score.

Recorded in: methodology 2026.09.6
IDCC-2026-0013Corrected2026-09-10Logged2026-09-14TypemethodologySeveritymaterial
Category: all categories
What was wrong

Every category promised a 30-day review cadence the work did not keep: oldest evidence ran to a median of 35 days, and 22 categories were overdue on 2026-09-10.

What was fixed

The published cadence is 45 days, and the overdue ceiling in the build fell from 7 to 3. Nothing was re-dated.

How it was caught

check-review-cadence-is-kept reported 22 overdue categories on 2026-09-10 with nothing changed but the clock.

Did the published order move?

No. No category changed order and no score moved.

Recorded in: methodology 2026.09.5
IDCC-2026-0012Corrected2026-09-09Logged2026-09-14TypescoringSeverityhigh
Category: Liquidity Management · Providers: Kodiak Islands, Steer Protocol Smart Pools, ICHI, Arrakis
What was wrong

liquidity_management published no cost basis, because its cost model charged a taker fee none of its products charge, while three of its records (Kodiak Islands, Steer and ICHI) already carried a rate in a verified note that the engine never read.

What was fixed

The category is priced on its own model, which charges the manager’s cut against the swap fees a position earns (Steer: $75 a year on a $10,000 position at 5% fee yield, not $1,500).

How it was caught

Not recorded in the changelog entry.

Did the published order move?

Yes. Among three rows tied at 66, rank 4 changed from Arrakis to ICHI, with Kodiak at 5 and Arrakis at 6; no score moved.

Recorded in: data changelog 2026-09-09-liquidity-management-reads-its-own-fees
IDCC-2026-0011Corrected2026-09-09Logged2026-09-14Typestale dataSeveritymaterial
Category: Trading Bots · Providers: Cryptohopper, Bitsgap, HaasOnline, 3Commas, Coinrule
What was wrong

Cryptohopper, Bitsgap and HaasOnline had raised their subscriptions while the records showed the old prices, Cryptohopper’s paper-trading free tier did not exist, Bitsgap’s real free plan was described as a trial, and 3Commas was said to publish no annual price.

What was fixed

Eight of nine records were re-read against the pages they cite. Cryptohopper, Bitsgap and HaasOnline had raised their prices and were corrected, 3Commas and Coinrule got smaller corrections, and Gunbot, Hummingbot and Freqtrade were confirmed unchanged. Pionex kept its old date because its citation no longer states its rate.

How it was caught

trading_bots was 117 days past its published review cadence and was re-read.

Did the published order move?

No. No published score or rank changed in any category; three personalised cases moved between rows tied on score.

Recorded in: data changelog 2026-09-09-trading-bots-re-read
IDCC-2026-0010Corrected2026-09-09Logged2026-09-14TypefactualSeveritymaterial
Categories: Stablecoin Yield, Liquid Staking, Yield Vaults · Providers: Sky Savings Rate (sUSDS), Ethena (sUSDe), Ondo USDY, PayPal PYUSD Rewards, Lido, Rocket Pool, Coinbase Staking
What was wrong

Four yields were filed as fees, so the cost column charged readers $1,126 to $1,280 a year of their own income, and thirteen cuts of rewards were charged against principal (Lido $3,200 a year instead of $160).

What was fixed

Each record sits in the field its verified note describes: a commission on rewards, a performance fee, or a gross yield that is never a cost basis.

How it was caught

Not recorded in the changelog entry.

Did the published order move?

No published score or rank moved. One published flag changed: stablecoin_yield.leaderSurvivesOnePointChange, true to false.

Recorded in: data changelog 2026-09-09-a-yield-is-not-a-fee
IDCC-2026-0009Corrected2026-09-09Logged2026-09-14TypescoringSeverityhigh
Category: Hardware Wallets · Providers: Coldcard, Ledger, Cypherock X1, Tangem
What was wrong

Two score ties in hardware_wallet (Coldcard and Ledger at 67, Cypherock X1 and Tangem at 62) were ordered on a pricing basis that mixed euros and dollars: BitBox’s €149 sat in a field read as US dollars, so €149 and $149 counted as the same price. BitBox itself was not in either tie.

What was fixed

A pricing basis that carries more than one currency may still display but no longer decides a tie.

How it was caught

Not recorded in the changelog entry.

Did the published order move?

Yes. In hardware_wallet two tied pairs swapped places (Ledger and Coldcard at 67, Tangem and Cypherock X1 at 62); no score changed, and BitBox did not move.

Recorded in: methodology 2026.09.4
IDCC-2026-0008Corrected2026-09-07Logged2026-09-14TypefactualSeverityhigh
Categories: Bridges, Stablecoins · Providers: Everclear (formerly Connext), USDS (Sky)
What was wrong

Everclear published a bridge fee of 0 and USDS a spread of 0, while each record’s own verification note said the figure could not be established.

What was fixed

Neither publishes a value on that basis and both render "not published on this basis"; twelve true zeros now name the costs they exclude.

How it was caught

Not recorded in the changelog entry.

Did the published order move?

Yes, in bridges: deBridge 56 to 59 and rank 9 to 8, Everclear 15 to 18, six rows moved. The published stablecoins order did not change. Corrected 2026-10-14: the other four rows that moved, at an unchanged score: Orbiter Finance #8 → #9 (59), Squid Router #16 → #15, Hop Protocol #17 → #16 and Symbiosis #18 → #17 (41 each).

Recorded in: data changelog 2026-09-07-unknown-is-not-zero
IDCC-2026-0007Corrected2026-09-06Logged2026-09-14TypescoringSeveritymaterial
Categories: Crypto Bill Pay, Fiat Rails & Banking for Crypto Businesses, Crypto Cards, Crypto Neobanks, Crypto Payroll, DeFi Insurance, DePIN Networks, Exchanges, Crypto Gift Cards, Institutional Custody, Institutional Execution Platforms, Key Recovery & Inheritance, Lightning Wallets, Money-Market Funds, Crypto Offramps, Onramps, Paid Crypto Research Seats, Payment Gateways, Perp House Vaults, Crypto Remittances, Restaking, Simple Buy, Stablecoin Yield, Crypto Subscriptions, Tokenised Bonds, Tokenised Equities, Tokenised Funds, Tokenised Real Estate, Tokenised T-Bills
What was wrong

For 33 of the 60 questionnaire countries the eligibility gate treated "not mapped" as eligible, so rows whose own market list omits the reader’s region were ranked for them; a restriction sentence was also matched as a substring, so "Niger" matched "Nigeria".

What was fixed

The gate reads the decision layer’s country verdict for every questionnaire country before scoring, and restriction sentences are matched word-bounded.

How it was caught

Not recorded in the changelog entry.

Did the published order move?

No published ranking changed (they are untouched by construction); 807 of 6,959 personalised country runs changed and 73 changed leader.

Recorded in: methodology 2026.09.3
IDCC-2026-0006Corrected2026-09-02Logged2026-09-14TypemethodologySeveritymaterial
Category: all categories
What was wrong

rankings.json published the base weights while each category was scored on re-weighted profiles, so only 98 of 934 products could be rebuilt from the file, and the gate certifying reconstruction never used the weights it read.

What was fixed

The file publishes the weight profile each category was scored with, and the gate rebuilds the weighted total and fails on a tampered, shifted or missing weight.

How it was caught

Found while measuring profileFit for the same methodology version; tampering with a published weight then showed the gate still passed (commit cb95c3fc).

Did the published order move?

Not recorded for this fix; all 934 products now reconstruct exactly.

Recorded in: methodology 2026.09.2
IDCC-2026-0005Corrected2026-09-02Logged2026-09-14TypescoringSeveritymaterial
Category: all categories
What was wrong

A stated priority for support raised profileFit, a dimension that could not move a result.

What was fixed

It raises frictionFit, where getting started and getting help are scored.

How it was caught

Found while measuring profileFit for the same methodology version (commit cb95c3fc).

Did the published order move?

Not recorded for this fix.

Recorded in: methodology 2026.09.2
IDCC-2026-0004Corrected2026-09-02Logged2026-09-14TypescoringSeveritymaterial
Category: all categories
What was wrong

The display rescale divided by a hardcoded 106 while the weights summed to 86, so published scores did not span the achievable range.

What was fixed

The divisor is derived from the weights.

How it was caught

Found while measuring profileFit for the same methodology version (commit cb95c3fc).

Did the published order move?

No. Every score rose by 0 to 5 points, median 4; no category changed order or leader.

Recorded in: methodology 2026.09.2
IDCC-2026-0003Corrected2026-09-02Logged2026-09-14TypescoringSeverityhigh
Categories: Crypto Bill Pay, Stablecoin Yield, Tokenised T-Bills, Tokenised Funds · Providers: Swapin (SwapinPay), Ethena (sUSDe)
What was wrong

With no country stated, the availability check matched an empty string against every market, which excluded bill_pay/swapin and stablecoin_yield/ethena_susde from every published ranking and awarded a primary-market bonus for a populated field.

What was fixed

The country match requires a stated country; both products returned and the catalog published 934 scored products, up from 932.

How it was caught

Not recorded in the changelog entry.

Did the published order move?

Yes. Two categories changed leader (tokenised_tbills, tokenised_funds) and six reordered below the top.

Recorded in: methodology 2026.09.1
IDCC-2026-0002Corrected2026-09-01Logged2026-09-14TypefactualSeverityminor
What was wrong

Eighteen surfaces advertised a methodology version that was never published: the year and month of the April release, without its patch number.

What was fixed

Every surface derives its version stamp from the methodology changelog.

How it was caught

Not recorded in the changelog entry.

Did the published order move?

Not recorded for this fix; the same version removed sentiment from the score, which reordered 8 of 114 categories.

Recorded in: methodology 2026.09.0
IDCC-2026-0001Corrected2026-04-27Logged2026-09-14TypefactualSeverityminor
Category: Crypto Cards · Provider: Bybit Card
What was wrong

The Bybit Card website URL carried a hardcoded /en-US/ path.

What was fixed

The path was removed.

How it was caught

Not recorded in the changelog entry.

Did the published order move?

Not recorded.

Recorded in: methodology 2026.04.0

This page prints the corrections numbered CC-2026-0001 to CC-2026-0020, in full. It is closed: no entry is added to it or taken from it. 20 corrections, logged 2026-09-14. All archive pages ·