The annotation reads — wallet trace:

• Initial deposit hashes to the TradeFXP receiving address at tradefxp.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.

Off-ramp reading — exchange counterparty for TradeFXP:

• TradeFXP 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 TradeFXP is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for TradeFXP — the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the TradeFXP casefile.

The Professor’s recovery note for TradeFXP:

1. Casefile review on TradeFXP — reading the submission against the no-go list.
2. Trace mapping on TradeFXP — pathway documented to chain-of-custody standard.
3. Off-ramp naming on TradeFXP — exchange endpoint identified.
4. Packet filing on TradeFXP — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on TradeFXP.

Chains and off-ramps the Professor follows:

• Chains in scope for TradeFXP — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for TradeFXP — named centralised exchanges with compliance leverage.
• Filings supported on TradeFXP — IC3, state AG, off-ramp desk, civil discovery as applicable.

What the Professor will never do — by policy:

• Boundary on TradeFXP — seed phrases are off-limits.
• Boundary on TradeFXP — remote logins are off-limits.
• Boundary on TradeFXP — upfront cash retainers are off-limits.
• Boundary on TradeFXP — guaranteed-recovery promises are off-limits.
• Boundary on TradeFXP — unsolicited outbound contact is off-limits.