Skip to main content

Public — correction log, archive

Corrections CC-2026-0121 to CC-2026-0140

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-0121 to CC-2026-0140, in full. It is closed: no entry is added to it or taken from it. 20 corrections, logged 2026-11-11. · All archive pages ·

IDCC-2026-0140Corrected2026-11-11Typestale dataSeverityhigh
Category: Crypto Cards · Provider: ether.fi Cash
What was wrong

ether.fi Cash was ranked first in crypto cards on its card agreement, its terms and its help-centre fee and country pages, each read by our research agent on 10 November 2026. ether.fi's terms of use say "you must not use any robots, spiders, crawlers, scrapers, or other automated tools or interfaces that are not provided by us to access the Website and extract data", and those pages are part of its website, so a read made that way cannot date the row. No read of it was made by a person.

What was fixed

ether.fi Cash leaves the ranking and is listed under "Not confirmed": "Re-read pending, its terms bar automated reads: ether.fi's terms bar robots, crawlers and scrapers on its website." Its earlier scores are not shown. It returns when a person reads its pages in a browser.

How it was caught

A review of every ranked row against the terms of the sites it was read from, under the rule that a site whose terms bar automated reading is read only by a person.

Did the published order move?

Yes. ether.fi Cash, first at 79, leaves with MetaMask Card (CC-2026-0138), Nexo Card (CC-2026-0139) and Coinbase Card (CC-2026-0145). We could read four of the nine crypto cards in full, and a ranking needs five, so crypto cards are not ranked right now (CC-2026-0151); Bleap Card, Crypto.com Card, Plutus Card and Zeal are listed without an order.

Recorded in: data changelog 2026-11-11-robots1-crypto-cards · src/lib/methodologySpecs/exclusions/cryptoCard.ts · src/lib/rereadPending.ts · src/lib/catalog/cryptoCardPool.ts
IDCC-2026-0139Corrected2026-11-11Typestale dataSeveritymaterial
Category: Crypto Cards · Provider: Nexo Card
What was wrong

Nexo Card was ranked fourth in crypto cards on its card page, card terms and status record, each read by our research agent on 10 November 2026. Nexo's platform terms bar causing or launching "any programs or scripts for the purpose of scraping, indexing, surveying, or otherwise data mining any portion of any of our programs, systems, or products", so a read made that way cannot date the row.

What was fixed

Nexo Card leaves the ranking and is listed under "Not confirmed": "Re-read pending, its terms bar automated reads: Nexo's terms bar programs or scripts that scrape or data-mine its products." Its earlier scores are not shown. It returns when a person reads its pages in a browser.

How it was caught

A review of every ranked row against the terms of the sites it was read from, under the rule that a site whose terms bar automated reading is read only by a person.

Did the published order move?

Yes, with ether.fi Cash and MetaMask Card in the same review: see CC-2026-0140.

Recorded in: data changelog 2026-11-11-robots1-crypto-cards · src/lib/methodologySpecs/exclusions/cryptoCard.ts · src/lib/rereadPending.ts
IDCC-2026-0138Corrected2026-11-11Typestale dataSeverityhigh
Category: Crypto Cards · Provider: MetaMask Card
What was wrong

MetaMask Card was ranked third in crypto cards, and would have been second once ether.fi Cash left, on its card page and its card help pages, each read by our research agent on 10 November 2026. MetaMask's terms of use, which govern its websites, bar users from any attempt to "use scraping techniques to mine or otherwise scrape data except as permitted by a Plan", so a read made that way cannot date the row.

What was fixed

MetaMask Card leaves the ranking and is listed under "Not confirmed": "Re-read pending, its terms bar automated reads: MetaMask's terms bar scraping data from its sites unless a plan permits it." Its earlier scores are not shown. It returns when a person reads its pages in a browser.

How it was caught

A second review of the rows next in line for a first place, against each row's own terms, before the new order was published.

Did the published order move?

Yes, see CC-2026-0140.

Recorded in: data changelog 2026-11-11-robots1-crypto-cards · src/lib/methodologySpecs/exclusions/cryptoCard.ts · src/lib/rereadPending.ts
IDCC-2026-0137Corrected2026-11-11Typestale dataSeverityhigh
Category: Crypto Offramps · Provider: Kraken
What was wrong

Kraken was ranked first in off-ramps on its fee schedule and its support pages on cash withdrawals and licensing, read by our research agent in October 2026. Kraken's general terms bar "any web scraping, web harvesting, or data extraction methods" and "any bots, robots, parsers, spiders, scripts" on its sites, so a read made that way cannot date the row. No read of it was made by a person.

What was fixed

Kraken leaves the off-ramp ranking and is listed under "Not confirmed": "Re-read pending, its terms bar automated reads: Kraken's terms bar bots, scripts and scraping on its pages." Its earlier scores are not shown. It returns when a person reads its pages in a browser.

How it was caught

A review of every ranked row against the terms of the sites it was read from, under the rule that a site whose terms bar automated reading is read only by a person.

Did the published order move?

Yes. Kraken, first at 82, leaves with Ramp Network (CC-2026-0136), MoonPay (CC-2026-0135) and Coinbase (CC-2026-0146). We could read three of the seven off-ramps in full, and a ranking needs five, so off-ramps are not ranked right now (CC-2026-0152); Banxa, Bitpanda and Transak are listed without an order.

Recorded in: data changelog 2026-11-11-robots1-offramps · src/lib/methodologySpecs/exclusions/offramps.ts · src/lib/rereadPending.ts · src/lib/trust/notRanked.ts
IDCC-2026-0136Corrected2026-11-11Typestale dataSeverityhigh
Category: Crypto Offramps · Provider: Ramp Network
What was wrong

Ramp Network was ranked second in off-ramps, and would have been first once Kraken left, on its fee and payout help pages and its licence page, read by our research agent in October 2026. Ramp's terms of service, which count its website among its services, say users won't "reverse engineer, copy, modify, data scrape, automate or re-sell any part of the Services", so a read made that way cannot date the row.

What was fixed

Ramp Network leaves the off-ramp ranking and is listed under "Not confirmed": "Re-read pending, its terms bar automated reads: Ramp's terms bar data scraping and automating any part of its services." Its earlier scores are not shown. It returns when a person reads its pages in a browser.

How it was caught

A second review of the row next in line for first place, against its own terms, before the new order was published.

Did the published order move?

Yes, see CC-2026-0137: off-ramps are not ranked right now.

Recorded in: data changelog 2026-11-11-robots1-offramps · src/lib/methodologySpecs/exclusions/offramps.ts · src/lib/rereadPending.ts
IDCC-2026-0135Corrected2026-11-11Typestale dataSeveritymaterial
Category: Crypto Offramps · Provider: MoonPay
What was wrong

MoonPay was ranked sixth in off-ramps on its pricing disclosure, licences page and help pages, read by our research agent in October 2026. MoonPay's terms of use say "you will not use an anonymizing proxy, or any other automatic devices, spider or manual processes to copy or monitor our websites without our prior written permission", so a read made that way cannot date the row.

What was fixed

MoonPay leaves the off-ramp ranking and is listed under "Not confirmed": "Re-read pending, its terms bar automated reads: MoonPay's terms bar spiders and automatic devices that copy its websites." Its earlier scores are not shown. It returns when a person reads its pages in a browser.

How it was caught

A second review of the off-ramp rows against their own terms, before the new order was published.

Did the published order move?

Yes, see CC-2026-0137: off-ramps are not ranked right now.

Recorded in: data changelog 2026-11-11-robots1-offramps · src/lib/methodologySpecs/exclusions/offramps.ts · src/lib/rereadPending.ts
IDCC-2026-0134Corrected2026-11-11Typestale dataSeverityhigh
Category: Transaction Simulation · Provider: MetaMask Transaction Shield
What was wrong

MetaMask Transaction Shield was ranked first in transaction simulation on its product page, its help article and a MetaMask news post, read by our research agent on 22 October 2026. MetaMask's terms of use, which govern its websites, bar users from any attempt to "use scraping techniques to mine or otherwise scrape data except as permitted by a Plan", so a read made that way cannot date the row.

What was fixed

MetaMask Transaction Shield leaves the ranking and is listed under "Not confirmed": "Re-read pending, its terms bar automated reads: MetaMask's terms bar scraping data from its sites unless a plan permits it." Its earlier scores are not shown. It returns when a person reads its pages in a browser.

How it was caught

A review of the other rows read from MetaMask's sites, after MetaMask Card was held for the same terms.

Did the published order move?

Yes. MetaMask Transaction Shield, first at 81, leaves; the rows next in line were held in the same review (CC-2026-0144), so no new first place was published and transaction simulation is not ranked right now (CC-2026-0150).

Recorded in: data changelog 2026-11-11-robots1-transaction-simulation · src/lib/methodologySpecs/exclusions/transactionSimulation.ts · src/lib/rereadPending.ts · src/lib/catalog/transactionSimulationPool.ts
IDCC-2026-0133Corrected2026-11-11TypescoringSeveritymaterial
Category: Crypto Cards · Provider: Crypto.com Card
What was wrong

Crypto.com Card was scored 7 of 10 on whose licence issues the card. Our scale gives 5-6 where the card agreement names the issuer but its register entry could not be reached and is recorded as unverified, and the Malta Financial Services Authority's register refused our request on 10 November 2026, so 7 sat above what the evidence shows.

What was fixed

Crypto.com Card's licence score will be 6 when crypto cards are ranked again, on the same evidence read on 10 November 2026: its card page and agreement name Foris MT Limited (C 90348) and its Visa Principal Member licence, and the register entry is recorded as unverified.

How it was caught

A second review of the card next in line for first place, read against the published scale.

Did the published order move?

No published order: crypto cards are not ranked right now (CC-2026-0151), so no score is shown; the licence score of 6 applies when they are ranked again.

Recorded in: data changelog 2026-11-11-robots1-crypto-cards · research-pending/rereads/2026-11-10-crypto_card.json · src/lib/methodologySpecs/cryptoCard.ts
IDCC-2026-0132Corrected2026-11-11Typestale dataSeveritymaterial
Category: Lightning Wallets · Provider: Misty Breez
What was wrong

Misty Breez was ranked as an operating Lightning wallet, with a link to a code repository that no longer exists, although its operator says on-chain and Lightning payments cannot be made in the app.

What was fixed

Misty Breez carries a sunset date: it is kept so holders can find the exit, with its criteria block at zero, it opens with a dated line that it no longer makes payments, per its operator, as of November 2026, and no page draws a Visit for it.

How it was caught

The November re-read of Lightning wallets, verified the same day against the operator's page and GitHub.

Did the published order move?

Misty Breez stays last of thirteen Lightning wallets and its score falls from 44 to 41; no other place or score changed. Misty Breez is removed from the Lightning wallet list on the country pages for Australia, Austria, Belgium, Canada, Finland, France, Germany, Hong Kong, Indonesia, Ireland, Italy, Japan, the Netherlands, Norway, the Philippines, Poland, Portugal, Singapore, South Korea, Spain, Sweden, Switzerland, Thailand, the United Arab Emirates, the United Kingdom, the United States and Vietnam, which list only products that operate.

Recorded in: data changelog 2026-11-11-lightning-wallets-misty-breez-stopped · scripts/check-no-dead-outbound-links.ts · tests/harm-3-shutdowns.test.ts
IDCC-2026-0131Corrected2026-11-11Typestale dataSeverityhigh
Category: Creator Mint Platforms · Provider: Fair.xyz
What was wrong

Fair.xyz was ranked sixth of nine creator mint platforms as a live deployer, with a link to its documentation, more than seven months after it closed on 27 March 2026.

What was fixed

Fair.xyz carries a sunset date of 27 March 2026: it is kept for reference with its criteria block at zero, it opens with a dated line that it closed on 27 March 2026, and no page draws a Visit for it.

How it was caught

The November re-read of creator mint platforms, verified the same day against Fair.xyz's own sunset notice.

Did the published order move?

Yes. Fair.xyz falls from sixth at 62 to ninth at 41, and thirdweb Contracts, Highlight and OpenSea Studio each move up one place, their scores unchanged; Art Blocks Engine stays first. Fair.xyz is removed from the creator mint platform list on the country pages for Australia, Austria, Belgium, Canada, Finland, France, Germany, Hong Kong, Indonesia, Ireland, Italy, Japan, the Netherlands, Norway, the Philippines, Poland, Portugal, Singapore, South Korea, Spain, Sweden, Switzerland, Thailand, the United Arab Emirates, the United Kingdom, the United States and Vietnam, which list only products that operate.

Recorded in: data changelog 2026-11-11-creator-mint-fair-xyz-sunset · scripts/check-no-dead-outbound-links.ts · tests/harm-3-shutdowns.test.ts
IDCC-2026-0130Corrected2026-11-11TypefactualSeveritymaterial
Category: Crypto-Backed Loans · Provider: Figure
What was wrong

Figure's record said the lender's own rights to reuse a borrower's collateral were unstated. Figure's own 2025 annual report states them: the collateral is in the company's control and it has the ability to rehypothecate, stake, lend or otherwise use it, though it does not have a practice of doing so, while its product page promises the collateral will never be rehypothecated.

What was fixed

Figure's tagline, description and first watch-out now quote the annual report, and a warning dated 11 November 2026 opens its watch-outs: the no-rehypothecation promise is a stated practice, not a prohibition.

How it was caught

The November re-read of crypto-backed loans, verified the same day against Figure's annual report on sec.gov.

Did the published order move?

No published score or place changed.

Recorded in: data changelog 2026-11-11-crypto-backed-loans-figure-reuse · src/lib/catalog/cryptoBackedLoansPool.ts · tests/harm-3-shutdowns.test.ts
IDCC-2026-0129Corrected2026-11-11Typestale dataSeveritymaterial
Category: Automation & Keepers · Provider: Chainlink Automation (migrating to Chainlink Runtime Environment)
What was wrong

Chainlink Automation's record did not open with the fact a buyer most needs: no upkeep has run on its Ethereum registry since 5 August 2026, its newer registries show only cancellations, and its successor needs Chainlink's approval to use.

What was fixed

Its record now opens its watch-outs with that warning, worded from chain reads of 11 November 2026.

How it was caught

The November re-read of automation and keeper networks, re-verified the same day on Ethereum.

Did the published order move?

No published score or place changed.

Recorded in: data changelog 2026-11-11-automation-chainlink-registry-idle · src/lib/catalog/automationKeepersPool.ts · tests/harm-3-shutdowns.test.ts
IDCC-2026-0128Corrected2026-11-11Typestale dataSeveritymaterial
Category: Sidechains · Provider: Chiliz Chain
What was wrong

Chiliz Chain's record said nothing of its Ethereum bridge escrow, which its bridge admins withdrew in full on 29 October 2026 and which held about 3% of that amount when read on 11 November 2026.

What was fixed

Chiliz Chain's record now opens its watch-outs with a warning that its bridge admins withdrew the whole Ethereum bridge escrow on 29 October 2026, that it now holds about 3% of that, and that a large exit to Ethereum may not be payable.

How it was caught

The November re-read of sidechains, verified the same day on Ethereum.

Did the published order move?

No published score or place changed.

Recorded in: data changelog 2026-11-11-sidechains-chiliz-bridge-escrow · src/lib/catalog/sidechainsPool.ts · tests/harm-3-shutdowns.test.ts
IDCC-2026-0127Corrected2026-11-11Typestale dataSeveritymaterial
Category: Lightning Payment Infrastructure · Provider: LNbits
What was wrong

LNbits' record carried no warning after LNbits said on 10 November 2026 that versions before 1.7.0 put funds at risk of theft.

What was fixed

LNbits' record now opens its watch-outs with a warning dated 11 November 2026: LNbits says versions before 1.7.0 put funds at risk, so update before use.

How it was caught

The November re-read of Lightning payment infrastructure, verified the same day against LNbits' own post and release.

Did the published order move?

No published score or place changed.

Recorded in: data changelog 2026-11-11-lightning-lnbits-security-update · src/lib/catalog/lightningPaymentInfrastructurePool.ts · tests/harm-3-shutdowns.test.ts
IDCC-2026-0126Corrected2026-11-11Typestale dataSeverityhigh
Category: Liquid Staking · Provider: Stride
What was wrong

Stride was ranked seventh of eleven liquid staking protocols at 65 as an operating protocol, with a link to stride.zone and a 10% reward commission, a month after its v35 upgrade froze liquid staking and began winding down the Stride chain on 12 October 2026.

What was fixed

Stride carries a sunset date of 12 October 2026: it is kept for reference with its criteria block at zero and no price, it opens with a dated warning that liquid staking is frozen, that the chain is winding down, that nobody should deposit and that funds follow Stride's announced process, and no page draws a Visit for it.

How it was caught

The November re-read of liquid staking, verified the same day against Stride's own release notes and a public Stride API.

Did the published order move?

Yes. Stride falls from seventh at 65 to eleventh at 41, and Frax Ether, Binance wBETH, Stader and Swell each move up one place, their scores unchanged; Jito stays first. Stride is removed from the liquid staking list on the country pages for Australia, Austria, Belgium, Canada, Finland, France, Germany, Hong Kong, Indonesia, Ireland, Italy, Japan, the Netherlands, Norway, the Philippines, Poland, Portugal, Singapore, South Korea, Spain, Sweden, Switzerland, Thailand, the United Arab Emirates, the United Kingdom, the United States and Vietnam, where it was seventh; those lists list only products that operate.

Recorded in: data changelog 2026-11-11-liquid-staking-stride-shut-down · scripts/check-dead-providers-unpriced.ts · tests/harm-3-shutdowns.test.ts
IDCC-2026-0125Corrected2026-11-11Typestale dataSeveritymaterial
Category: Appchains / L3s · Provider: Abstract
What was wrong

Abstract was ranked first of nine app-chains and L3s with no word that it is shutting down, although its own terms, updated on 6 October 2026, say it is being wound down and its migration page gives users until 15 December 2026 to move their assets off it.

What was fixed

Abstract's record now opens its watch-outs with a warning dated 11 November 2026: it shuts down on 15 December 2026, assets should be moved off before then, and its terms say assets left behind cannot be moved and no recovery is promised.

How it was caught

The November re-read of app-chains and L3s, verified the same day against Abstract's own terms and migration page.

Did the published order move?

No published score or place changed; Abstract stays first of nine.

Recorded in: data changelog 2026-11-11-appchains-abstract-wind-down · src/lib/catalog/appchainsL3sPool.ts · tests/harm-3-shutdowns.test.ts
IDCC-2026-0124Corrected2026-11-11Typestale dataSeverityhigh
Category: L2 Blockchains · Provider: Blast
What was wrong

Blast was ranked thirteenth of fifteen layer-2 chains at 47 as an operating chain, with a link to blast.io, after its Ethereum portal was paused on 3 November 2026 and its last state root was posted on 6 November 2026; its RPC and documentation hosts no longer resolve and blast.io now serves a fund-recovery page.

What was fixed

Blast carries a sunset date of 3 November 2026: it is kept for reference with its criteria block at zero so holders can find the recovery route, it opens with a dated warning that the chain is paused, that withdrawals go through Blast's fund-recovery process and that nobody should bridge in, and no page links to blast.io.

How it was caught

The November re-read of layer-2 chains, independently verified the same day on Ethereum and in DNS.

Did the published order move?

Yes. Blast falls from thirteenth at 47 to fourteenth at 41 and Manta Pacific moves from fourteenth to thirteenth, its score unchanged; no other place or score changed and Arbitrum One stays first. Blast is removed from the layer-2 chain list on the country pages for Australia, Austria, Belgium, Canada, Finland, France, Germany, Hong Kong, Indonesia, Ireland, Italy, Japan, the Netherlands, Norway, the Philippines, Poland, Portugal, Singapore, South Korea, Spain, Sweden, Switzerland, Thailand, the United Arab Emirates, the United Kingdom, the United States and Vietnam, which list only products that operate.

Recorded in: data changelog 2026-11-11-l2-chains-blast-shut-down · scripts/check-no-dead-outbound-links.ts · tests/harm-3-shutdowns.test.ts
IDCC-2026-0121Corrected2026-11-11TypefactualSeverityhigh
Category: Cross-Chain Swaps · Providers: Across, Relay, Squid, deBridge, LI.FI / Jumper
What was wrong

On 10 November 2026 at 2:05 p.m. ET (19:05 UTC) Across posted on its own X account that users should not visit its app, connect wallets or sign transactions while it investigates a possible security incident affecting its domain (as reported by Cointelegraph and The Defiant the same day). By 22:05 UTC across.to, app.across.to and docs.across.to no longer resolved. Cross-chain swaps still ranked Across second (score 78), with a link to across.to on its row.

What was fixed

From 00:48 UTC on 11 November 2026 (an emergency step) the rows stayed ranked with a dated warning and no link to across.to; this correction takes them out of the ranking. Across leaves the ranking as a pending re-read. It is listed under "Not confirmed" with the line "Re-read pending: Across says across.to was taken over through its registrar on 10 November 2026; its post-mortem is not out yet". No page links to across.to or its subdomains while it is held: they are listed in data/outbound-blocked-hosts.json, which the build checks every outbound link against, and its review and two comparison guides are withdrawn. It returns, re-scored, once Across publishes its post-mortem on its own site (root cause, hijack window, contracts unaffected), the domain stays clean for 7 days after it, and the row is read live on its own pages. That leaves four cross-chain swap products, each read in full on 3 November 2026, and a ranking here needs five, so the category is not ranked right now: its page lists deBridge, LI.FI / Jumper, Relay and Squid listed alphabetically, with no rank, no first place and no scores, and says what left and why.

How it was caught

Reports of Across’s warning on 10 November 2026 (Cointelegraph, The Defiant), checked the same evening against the domain itself: across.to did not resolve to an address and app.across.to and docs.across.to answered NXDOMAIN.

Did the published order move?

Yes. Cross-chain swaps publishes no order while it is not ranked; until 11 November 2026 it had Relay first (80), Across second (78), Squid third (68), deBridge fourth (65) and LI.FI / Jumper fifth (65). In the 27 country lists (Australia, Austria, Belgium, Canada, Finland, France, Germany, Hong Kong, Indonesia, Ireland, Italy, Japan, the Netherlands, Norway, the Philippines, Poland, Portugal, Singapore, South Korea, Spain, Sweden, Switzerland, Thailand, the United Arab Emirates, the United Kingdom, the United States and Vietnam) Relay leaves first place and Across second, and each list shows nothing while the category is not ranked.

Recorded in: data changelog 2026-11-10-across-reread-pending · src/lib/rereadPending.ts · data/outbound-blocked-hosts.json · src/lib/trust/notRanked.ts
IDCC-2026-0123Corrected2026-11-10Logged2026-11-11TypefactualSeveritymaterial
Category: P2P Exchanges · Provider: NoOnes
What was wrong

NoOnes' record listed no restricted market, so readers in Germany and 14 other countries we cover were told that no restriction naming their country was found and were given a link to the provider. NoOnes' own list of blocked jurisdictions, which its terms point to, blocks the United States and the United Arab Emirates and, effective 1 July 2026, serves no resident of the 27 EU states, Iceland, Liechtenstein or Norway. In September that list answered only as an empty script shell and we kept the field blank and said so; on 10 November 2026 it answered in full.

What was fixed

NoOnes' record names the 15 countries we cover that it does not serve and quotes its list with its date, and its page reads "Restricted in" those countries with no provider link. The remaining EU states and the US territories on the list are quoted in the record's availability note.

How it was caught

The November cadence re-read of P2P exchanges, independently verified the same evening against the provider's terms and help centre.

Did the published order move?

No published score or worldwide place changed; NoOnes stays seventh of 8. NoOnes leaves the P2P exchange lists for Austria, Belgium, Finland, France, Germany, Ireland, Italy, the Netherlands, Norway, Poland, Portugal, Spain and Sweden (where it was sixth), the United Arab Emirates (seventh) and the United States (fourth); in each of those 15 lists OKX P2P moves up one place, and every other row keeps its order apart from Peach Bitcoin's move from third to fifth (CC-2026-0122).

Recorded in: data changelog 2026-11-10-p2p-exchanges-harm · src/lib/catalog/p2pExchangesPool.ts · src/lib/providerCountryFilter.ts
IDCC-2026-0122Corrected2026-11-10Logged2026-11-11Typestale dataSeverityhigh
Category: P2P Exchanges · Provider: Peach Bitcoin
What was wrong

Peach Bitcoin was ranked third of 8 P2P exchanges on a 2-of-2 multisig escrow in which Peach held one key, scored 7/10 on who can move the coins while the trade is open and 7/10 on what the platform promises when a trade goes wrong. On 31 August 2026 Peach paused that escrow while a Swiss regulatory review runs; its homepage now states that the seller fully controls the escrowed bitcoin, and its founder's post says Peach no longer holds a signature in the escrow. Our page kept the old description and scores for ten weeks.

What was fixed

Peach's escrow control is scored 3/10 and its dispute standard 4/10, from Peach's own homepage notice and its founder's post of 31 August 2026, read on 10 November 2026; the description, strengths and watch-outs say that the seller alone controls the coins, that only sellers with a long record may sell, and that the 2% fee still applies. The terms, last updated 1 July 2026, still describe the 2-of-2 escrow. The rest of Peach's record keeps its 24 September 2026 read.

How it was caught

The November cadence re-read of P2P exchanges, independently verified the same evening against the provider's pages.

Did the published order move?

Yes, in P2P exchanges: Peach Bitcoin falls from third (63) to fifth (52); RoboSats moves from fourth to third (62) and LocalCoinSwap from fifth to fourth (53), their scores unchanged. Hodl Hodl stays first and Bisq second. Peach moves the same way, from third to fifth behind RoboSats and LocalCoinSwap, in all 24 country lists that carry it.

Recorded in: data changelog 2026-11-10-p2p-exchanges-harm · src/lib/methodologySpecs/p2pExchanges.ts · src/lib/catalog/p2pExchangesPool.ts

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