Encyclopedia Stablecoins · Entry 134

Sent a stablecoin on the wrong network: what to check

Degrees of Satoshi editorial projectAI-assisted research · separate automated verificationCorrections

Theme: Stablecoins
Sources: 7 cited records
Reading time: About 3 minutes
Automated verification: 2 October 2026
Substantive update: 2 October 2026

In this article

At a glance

Key facts

Key facts for Sent a stablecoin on the wrong network: what to check
Fact	Detail	Source
Ledger	Balances and transaction histories are chain-specific.	[2]
Deployment	A stablecoin can have different official contracts on different networks.	[3]
Authority	Moving an asset requires the destination’s actual spending authorization.	[1]

Find the transaction on the chain used

Record the transaction hash, chain, destination and token contract. Confirm that a transfer actually succeeded before describing it as a recovery case.

A missing balance in one wallet view can be a display issue, an unsupported asset or an actual transfer to an uncontrolled destination. Those situations require different evidence.

Distinguish self-custody from a service deposit

If the same signing authority controls the destination on the relevant network, a supported wallet may be able to interact with the asset there. Contract accounts and custodial deposit addresses require additional care; their behavior and deployment can differ by chain.

For a service-controlled deposit, only that service can assess its systems and available recovery process. Possessing the transaction hash does not give the sender authority to move the received tokens.

A later bridge is a separate transaction

If the asset is accessible, moving it to another chain requires a supported transfer mechanism with its own fees and dependencies. Selecting another network in the interface is not that mechanism.

Do not give a recovery service a seed phrase or assume that every claimed bridge supports the exact token variant. Establish the actual route first.

Direct answers

Questions people ask

Will an address checksum prevent a wrong-network transfer?

An EIP-55 checksum checks address formatting, not which network the recipient or service supports. The same address bytes can be displayed on several compatible chains.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

A stablecoin sent on the wrong network is recorded on the network actually used. Switching a wallet’s display does not move it to the intended chain. Recovery depends on who controls the destination, whether the token and network are supported, and whether a valid authorized recovery path exists; it is not guaranteed.

Scope: Stablecoins · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.

Link to this claim

Ledger: Balances and transaction histories are chain-specific.

Scope: Stablecoins · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.

Link to this claim

Deployment: A stablecoin can have different official contracts on different networks.

Scope: Stablecoins · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.

Link to this claim

Authority: Moving an asset requires the destination’s actual spending authorization.

Scope: Stablecoins · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.

Link to this claim

Revision history

2026-10-02 — First publication after primary-source research and independent automated verification.

Source register

Sources and references

Retrieval dates and locators are recorded individually.

Ethereum accountsethereum.org contributors
Key-controlled and code-controlled accounts, balances, nonces and storage.
Locator: Account types; An account examined; Account creation · Retrieved: 2026-10-02T17:03:41.958ZOpen source
Ethereum JSON-RPCethereum.org contributors
RPC response fields, transaction receipts, call simulation and log filtering.
Locator: eth_getTransactionByHash; eth_getTransactionReceipt; eth_call; eth_getLogs; eth_getCode; eth_estimateGas; eth_getBalance; eth_getStorageAt; eth_getTransactionCount; default block parameter · Retrieved: 2026-10-02T17:03:42.060ZOpen source
USDC Contract AddressesCircle
Network-specific canonical contract identifiers and the distinction from test deployments.
Locator: Mainnet; Testnet · Retrieved: 2026-10-02T17:03:43.107ZOpen source
USDC TermsCircle
Non-EEA USDC holder terms, eligibility, redemption and restrictions; not an unconditional promise to every holder.
Locator: Sections 1–4, 8, 13, 15–17 · Retrieved: 2026-10-02T17:03:43.080ZOpen source
CCTP overviewCircle
Native USDC transfer uses source-chain burning, Circle attestation and destination minting.
Locator: How CCTP works; Burn and mint · Retrieved: 2026-10-02T17:03:43.290ZOpen source
Mixed-case checksum address encodingEthereum Improvement Proposals
Capitalization encodes a checksum without changing the address bytes.
Locator: Specification; Rationale; Test Cases · Version / scope: EIP/ERC-55; retrieved document hash recorded · Retrieved: 2026-10-02T17:03:42.205ZOpen source
Simple replay attack protectionEthereum Improvement Proposals
Transaction chain ID domain separation; not blanket protection for all signatures.
Locator: Specification · Version / scope: EIP/ERC-155; retrieved document hash recorded · Retrieved: 2026-10-02T17:03:42.312ZOpen source

How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

Degrees of Satoshi editorial project. “Sent a stablecoin on the wrong network: what to check.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/stablecoin-wrong-network/