# Free lead magnet: Wrong-network USDC recovery checklist

Practical self-custody steps when USDC (or something labeled “USDC”) lands on the **wrong network**, **wrong contract**, or **wrong destination**. Legal ops only.

**Hard rule:** Never paste a seed, private key, keystore, or hardware PIN into a website, chat, agent prompt, or “recovery form.” Agents may draft notes; **humans** confirm explorers and sign.

**Also free:** [Base USDC receive checklist](./BASE-USDC-CHECKLIST.md) · [How to pay on Base](./HOW-TO-PAY-USDC-BASE.md) · [Payment-proof email](./payment-proof-email.md)  
**Sales:** http://bore.pub:19509/

Operational guidance only — some mis-sends are unrecoverable. Prefer prevention.

---

## 0. Stop-the-bleed (first 60 seconds)

- [ ] Stop signing. Close “Support / Recovery / Unlock USDC” tabs.
- [ ] Ignore DMs that claim they saw your failed tx and can fix it for a fee.
- [ ] Do not connect your main wallet to a stranger’s dApp link.
- [ ] Open an explorer **you typed** (basescan.org, etherscan.io) — not Discord/Telegram links.
- [ ] Note offline: intended vs actual chain, tx hash, amount, token contract, to-address, your receive address, time + timezone.

Pressure to “act in five minutes or funds are gone” is a scam signal, not a deadline.

---

## 1. Collect facts

| Field | Verify |
|-------|--------|
| Tx hash / status | Explorer you typed |
| Chain landed vs intended | Hostname + chain id (Base = `8453`) |
| Token **contract** | Token page — ignore the “USDC” label alone |
| Amount, from, to | Logs; EOA / contract / CEX? |
| Control of `to` on that chain? | yes / no / unknown |

**Native Circle USDC on Base (re-verify):** `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`

Evidence pack: explorer page (hash visible), contract as text, your pay instructions, payer’s claimed network.

---

## 2. Classify (one primary class)

### A — Wrong chain, same address, you hold the key

Official USDC on another EVM to the same `0x` you use on Base.

- [ ] Source-chain explorer: `to` is yours, success.
- [ ] Switch your normal wallet to that network; add **official** USDC for that chain only.
- [ ] Hold, or bridge/withdraw via a path you already trust (URL from docs, not DMs). Tiny test if new.
- [ ] Never export the key into a “multi-chain recovery” site.

### B — Wrong USDC contract on the correct chain

- [ ] Contract ≠ official → treat as **non-payment** until native USDC arrives.
- [ ] Hide spam; no unlimited approvals; no unknown routers.
- [ ] Reply with expected contract + request resend. Log both txs.

### C — Sent to a protocol/contract

Reputable app → **official docs / support ticket only**. Unverified bytecode → high loss risk; no stranger “rescue” signatures.

### D — CEX deposit, wrong network / missing memo

No second deposit “to unlock.” Ticket on the exchange’s **bookmarked** site with hash, amount, asset, network. Ignore DM support clones.

### E — You do not control `to`

Typo / wrong paste / abandoned address. Usually **unrecoverable**. Confirm old hardware/seed/multisig once, then write off or ask the recipient (social, not crypto). If *you* published the wrong address, fix every BUY/invoice the same day.

### F — Failed or stuck pending

Confirm on explorer. Failed → funds usually still with sender (minus gas). Stuck → speed-up/cancel on the **same** nonce. Never paste a seed to “unstick.”

---

## 3. Short playbooks

**A1:** View official USDC on source chain → bridge only if you need Base → confirm destination is native Base USDC → update payer copy (Base · 8453 · contract · address · invoice id).

**B1 (seller):** Do not deliver. Send expected vs actual. Ask for a **new** correct payment. Refund mistaken asset only if you can safely return same chain/token (minus costs) — never via a DM “verify” address. Deliver after Basescan: success + correct contract + correct to + correct amount.

**D1:** Official ticket only. No seed/2FA backups. Calendar-remind; keep receiving on a clean address.

---

## 4. Scam filter — abort if any appear

- Fake “BaseScan / Circle / MetaMask / Coinbase support” DMs
- “Sync wallet” / “enter 12 words to reverse the tx”
- Random “reclaim bridged USDC” connect links
- Urgency + secrecy; recovery fee to a personal EOA with no ticket
- Remote desktop “help”; unlimited USDC/permit for a random spender

**Allowed:** official exchange tickets, official bridge UIs from docs, your wallet’s network switch, hired pros with a written engagement (**still never give them your seed**).

---

## 5. Incident log + prevention

```
Incident ID: WNR-YYYYMMDD-##
Timezone: Europe/Copenhagen (note UTC offset)
Opened: / Closed:
Intended: chain / asset / amount / invoice
Actual: chain / token contract / amount / tx hash
Class: A / B / C / D / E / F
Destination controlled by us? yes/no
Actions: …
Outcome: recovered to Base / on source / CEX pending / written off
Final tx hashes: …
BUY/invoice change? Scam contacts blocked?
Operator:
```

**Prevention:** Always publish Base (8453) + native USDC contract + address + invoice id. Large first-time pays → test send. Prefer tx-hash proof. Humans verify address first 6 + last 4 before publish. Re-check Circle/Base USDC docs quarterly.

**Payer share template:**

```
Please pay on Base (chain id 8453).
Asset: USDC (native Circle)
USDC contract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Address: 0xYOUR_PUBLIC_ADDRESS_HERE
Invoice: INV-____
After send, reply with the transaction hash.
Do not send on Ethereum mainnet or other L2s unless we explicitly agree in writing.
```

---

## 6. Decision tree

1. Successful on typed explorer? → No → Class F.  
2. Official USDC for that chain? → No → Class B.  
3. You control `to`? → No → E / D / C.  
4. Yes + wrong chain → Class A.  
5. Yes + right chain + official USDC + correct amount → normal delivery.  
6. Seed / blind signature request → **abort**.

---

## Upgrade path (same wallet)

| Need | Amount |
|------|--------|
| This magnet + [receive checklist](./BASE-USDC-CHECKLIST.md) | Free |
| [Board gate](./fixed-pay-board-gate.md) / [WHICH-SKU](./WHICH-SKU.md) | Free |
| Agent Bounty Claim Checklist | **9 USDC** |
| Fixed-Pay Hunt Playbook | **15 USDC** |
| Ops Pack (tracker, pitches, cadence, scam filter) | **19 USDC** promo (list 29) |

Pay native USDC on Base to `0x0Ae3CC597f332906f29bBd24b57bDEb60C0a95B3` → email tx hash to `kasperwallet@outlook.com`. Steps: [HOW-TO-PAY-USDC-BASE.md](./HOW-TO-PAY-USDC-BASE.md).

Slow down, classify, use official surfaces, test small, document, harden the template. Never trade your seed for a recovery story.