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

• On the Mexsus Limited 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 Mexsus Limited is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the Mexsus Limited casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, Mexsus Limited escalates to IC3, state AG, and civil-discovery overlay.

How a Mexsus Limited casefile becomes a evidence filing:

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

What we read in a Mexsus Limited casefile:

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