# Sent a stablecoin on the wrong network: what to check

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.

Evidence: [Ethereum accounts](https://ethereum.org/en/developers/docs/accounts/); [Ethereum JSON-RPC](https://ethereum.org/en/developers/docs/apis/json-rpc/); [USDC Contract Addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses); [USDC Terms](https://www.circle.com/legal/usdc-terms)

Canonical: https://degreesofsatoshi.com/encyclopedia/stablecoin-wrong-network/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T18:15:23.891Z
Data current through: 2026-10-02

AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied.

## Key facts

- **Ledger:** Balances and transaction histories are chain-specific. ([Ethereum JSON-RPC](https://ethereum.org/en/developers/docs/apis/json-rpc/))
- **Deployment:** A stablecoin can have different official contracts on different networks. ([USDC Contract Addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses))
- **Authority:** Moving an asset requires the destination’s actual spending authorization. ([Ethereum accounts](https://ethereum.org/en/developers/docs/accounts/))

## 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.

Evidence: [Ethereum JSON-RPC](https://ethereum.org/en/developers/docs/apis/json-rpc/); [USDC Contract Addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses)

## 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.

Evidence: [Ethereum accounts](https://ethereum.org/en/developers/docs/accounts/); [USDC Terms](https://www.circle.com/legal/usdc-terms)

## 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.

Evidence: [CCTP overview](https://developers.circle.com/cctp)

## Questions

### 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.

Evidence: [Mixed-case checksum address encoding](https://eips.ethereum.org/EIPS/eip-55); [Simple replay attack protection](https://eips.ethereum.org/EIPS/eip-155)

## Claims and scope

### stablecoin-wrong-network-quick-answer

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: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null}

### stablecoin-wrong-network-fact-ledger

Ledger: Balances and transaction histories are chain-specific.

Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null}

### stablecoin-wrong-network-fact-deployment

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

Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null}

### stablecoin-wrong-network-fact-authority

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

Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null}

## Sources

- [Ethereum accounts](https://ethereum.org/en/developers/docs/accounts/) — ethereum.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.958Z.
- [Ethereum JSON-RPC](https://ethereum.org/en/developers/docs/apis/json-rpc/) — ethereum.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.060Z.
- [USDC Contract Addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses) — Circle. Network-specific canonical contract identifiers and the distinction from test deployments. Locator: Mainnet; Testnet. Retrieved: 2026-10-02T17:03:43.107Z.
- [USDC Terms](https://www.circle.com/legal/usdc-terms) — Circle. 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.080Z.
- [CCTP overview](https://developers.circle.com/cctp) — Circle. 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.290Z.
- [Mixed-case checksum address encoding](https://eips.ethereum.org/EIPS/eip-55) — Ethereum Improvement Proposals. Capitalization encodes a checksum without changing the address bytes. Locator: Specification; Rationale; Test Cases. Retrieved: 2026-10-02T17:03:42.205Z.
- [Simple replay attack protection](https://eips.ethereum.org/EIPS/eip-155) — Ethereum Improvement Proposals. Transaction chain ID domain separation; not blanket protection for all signatures. Locator: Specification. Retrieved: 2026-10-02T17:03:42.312Z.

## Revision history

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

## Cite this entry

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/