Off-ramp map, where the funds left the chain:

• AxianceFX off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The AxianceFX off-ramp address is matched to known compliance feeds, the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for AxianceFX, the packet meets the off-ramp’s published compliance standard.
• When the AxianceFX off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

How a AxianceFX casefile becomes a evidence filing:

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

Reading-list, chains and exchanges in scope:

• Deposit + forwarding chains for AxianceFX, Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
• Off-ramps the AxianceFX casefile may resolve to, centralised exchanges that respond to compliance filings.
• Filing pathways on AxianceFX, IC3, state AG, off-ramp compliance, and civil-discovery overlay.

Lines the Professor will not cross:

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