The annotation reads, wallet trace:

• Initial deposit hashes to the Expattradings receiving address at expattradings.com.
• Hop-by-hop forwarding wallets across the deposit chain, captured with chain of custody hashes.
• Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
• Obfuscation events through mixer contracts and privacy services.
• Centralised-exchange off-ramp wallets, the named counterparty that holds compliance leverage.

The Professor’s off-ramp note:

• Expattradings casefiles end at a centralised exchange, Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for Expattradings is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for Expattradings, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Expattradings casefile.

Recovery sequence, from on-chain reading to filed packet:

1. Read the Expattradings submission, written go/no-go returned.
2. Map the Expattradings wallet trail, every hop captured with chain of custody hashes.
3. Name the Expattradings off-ramp, endpoint counterparty identified.
4. Build and file the Expattradings recovery packet, to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the Expattradings file, until written next steps exist.

Boundaries on every Expattradings casefile, never crossed:

• What the Professor will not do on Expattradings, ask for a seed phrase.
• What the Professor will not do on Expattradings, request remote-access logins.
• What the Professor will not do on Expattradings, demand cash up front.
• What the Professor will not do on Expattradings, promise a guarantee.
• What the Professor will not do on Expattradings, call you out of the blue.