Exchanges are quietly dropping stablecoin rails. Here is the dated log.

Pennyforge — Thu, 27 Aug 2026 15:53:17 +0000

On August 17, 2026, Coinbase stopped accepting USDC on the Noble network. If you sent USDC to your Coinbase address on Noble after that date, the status page says these funds "will not be recoverable." No rescue route published. One dated line on a status board. What did not change: Circle still issues USDC on Noble, and Coinbase USDC remains supported on Ethereum, Base, Solana, Arbitrum, Optimism and Polygon. One rail was dropped, not the token.

We have been following it since day 1. We run a small studio and we built SendCheck, a free checker that reads a crypto address before you send it. The Noble incident is why the third tab of our site exists, and today we are publishing the log we kept along the way: which platforms stopped supporting which rails, with dates, so the pattern is easier to see than one status page at a time.

Three ways a stablecoin send can go wrong

Wrong variant. USDC and bridged USDC.e are different tokens that look identical in a wallet. On Polygon we measured about $998M of the bridged version against about $618M of the native one (1.6x, on-chain read on Aug 19).
Wrong chain. Same address string, different network.
Rail sunset. The token is right, the address is right, the network is right. But the receiving platform quietly stopped supporting that network. No checksum or variant check catches this. Only the receiver's current network list does.

The first two you can check yourself. The third one you can only verify by asking: does the receiver still support this network today?

The dated log

Date	Platform	What stopped	Note
2026-08-17	Coinbase	USDC on Noble	post-cutoff funds "will not be recoverable" per the status page
2026-08-17	Coinbase	DAI on Arbitrum, Avalanche, Optimism	Ethereum only
2026-08-15	Coinbase Wallet (Base app)	a batch of networks (DOGE, LTC, zkSync Era, "and other unsupported networks")	assets safe, import to move
2026-08-05	OKX	USDT deposits on BSC	official help page; BNB unaffected
2026-04-07	Binance	DAI deposits and withdrawals	legacy BEP-20 DAI swapped 1:1 to USDS

Every row above has a source in our Rail Watch matrix. The method is deliberately boring: a cell counts as "supported" only if the platform's own page or status page lists the network, as of the check date.

What the Noble story actually showed

The verified timeline:

Aug 14: Coinbase announces the Noble USDC cutoff.
Aug 17: the cutoff. Deposits and withdrawals on Noble are closed.
Aug 19: the status incident is published. It still reads "Resolved" as of Aug 27, with the text unchanged: "Please do not send USDC to your Coinbase deposit addresses on the Noble network after August 17, 2026 as these funds will not be recoverable."
As of Aug 25: Circle's own guide for getting USDC on Noble still directed readers to Coinbase, eight days after the cutoff. The sender's documentation pointed users at a rail the receiver had just dropped.
Aug 26: Circle's guide stops naming Coinbase. It now says "digital asset exchanges" and lists non-custodial wallets. The wording got vaguer, but no specific replacement custodial route was named.
Aug 27 (day 10): zero documented user losses, and no rescue route published.

The numbers: roughly $132M of USDC sat on Noble as of July 15. The Aug 18 snapshot showed about $114M issued, $93M bridged out, and about $21M still on-network.

And there is a second clock on this rail: Noble still runs on legacy CCTP V1, which Circle is phasing out on a roughly ten-month schedule from July 2026. That lands around May 2027.

Why nobody catches these

Exchange network support pages are human-curated status boards. They are not queryable APIs, they have no change feeds, and the "as of" date is often invisible. The check that saves money is simple: do both ends of the send still support this network today? Nobody was keeping it in one place. So we are.

Rail Watch: the matrix we keep

The third tab of SendCheck is a platform x token x network support matrix (Coinbase, Kraken, Binance, OKX, Gemini, Bybit, across USDC, USDT, DAI and EURC on eleven networks). Every cell carries a confidence rating, an as-of date and a source link. Under the matrix sits a dated change feed, and the whole thing is also available as machine-readable JSON.

What we are watching next

The first documented Noble loss and its amount. Day 10 is zero, and that changes the story if it moves.
A Coinbase rescue route for stranded custodial Noble USDC.
Circle naming a specific custodial replacement for Noble USDC.
The CCTP V1 phase-out timing.

The log is public at https://sendcheck.surge.sh/rails.html. Every cell has a date and a source, so check it yourself. If a platform changed something and we missed it, the correction line on that page is how we hear about it.

I built a free checker that reads a crypto address before you send (SendCheck)

Pennyforge — Thu, 27 Aug 2026 11:55:41 +0000

Hey dev.to — Pennyforge here, a one-person studio that builds small, useful tools that replace SaaS. Today I'm sharing our first product: SendCheck, a free tool that checks a crypto address before you send, so the worst-case finding is "looks wrong" instead of "your USDC is gone".

The pain

Sending crypto is one-way. Paste the wrong address, or send USDC on a network the receiving exchange doesn't listen to, and there is no support ticket and no undo. I kept seeing the same story in crypto help communities: hundreds of dollars, one wrong paste, gone. So I built the check I wished I had, runnable in a few seconds in the browser.

What it checks (free, no account)

Format + checksum: is it a valid address for the chosen chain, and is the casing EIP-55-correct?
Has it ever been used? A nonce check against public RPC. A never-used address earns a caution, not an error (receive-only addresses legitimately sit at nonce 0), but it is good to know before your savings are the first thing it ever holds.
Contract or wallet? Every address gets labelled as one or the other, so sending to a contract happens on purpose.
USDC variant check: on Base, USDC and bridged USDC.e have different addresses and different behavior; the tool tells you which one you are looking at, on every network it supports.
Rail watch: per-exchange, per-token, per-network support matrix (Coinbase, Kraken, Binance, OKX, Gemini, Bybit), with a confidence rating on every cell, dated change entries, and sources.

How it works

Everything runs in your browser. The page talks directly to public RPC endpoints for Base, Ethereum, Arbitrum, Optimism and Polygon, and cross-checks against a curated table of canonical token addresses. Your address never touches our servers; the whole site is static.

Pro (0.50 USDC, one-time)

Free gets you three checks a day; Pro is unlimited checks on this browser for 0.50 USDC, once. Pay in USDC and we verify it on-chain: the check reads the USDC Transfer logs of your transaction and confirms the USDC actually reached our wallet. No screenshots, no trust. Refund = the exact USDC back to your address, on-chain.

Sharing

Every check gets a share link. The link is a pointer, not a snapshot: whoever opens it gets a fresh, live re-run in their own browser, and shared checks are free for them. It turns "here's a screenshot of what I found" into "here, run it yourself".

Try it: https://sendcheck.surge.sh

Feedback is welcome — I read every comment. And if it ever catches a bad address before you lose money, the tip section at the bottom of the page (USDC on Base) is real, but the "it caught it" replies mean more.

DEV Community: Pennyforge