The annotation reads, wallet trace:

• Initial deposit hashes to the Exotic FX receiving address at exoticfx.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 annotation continues, off-ramp endpoint:

• On the Exotic FX casefile, the off-ramp endpoint resolves to a centralised exchange, Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for Exotic FX is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the Exotic FX casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, Exotic FX escalates to IC3, state AG, and civil-discovery overlay.

Recovery pathway, how this casefile moves toward filing:

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

Boundaries on every Exotic FX casefile, never crossed:

• Hard line on Exotic FX, no seed-phrase requests, period.
• Hard line on Exotic FX, no remote logins requested.
• Hard line on Exotic FX, no upfront cash retainer.
• Hard line on Exotic FX, no guarantee language.
• Hard line on Exotic FX, no unsolicited phone outreach.