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

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

The Professor’s recovery note for LeonMarkets:

1. Casefile triage on LeonMarkets, the submission is read; a written assessment is delivered.
2. Forensic trace on LeonMarkets, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the LeonMarkets endpoint is named.
4. Recovery filing on LeonMarkets, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of LeonMarkets, the Professor follows the casefile until next-step documentation exists.

Chains and off-ramps the Professor follows:

• Chains the Professor reads for LeonMarkets casefiles, BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in LeonMarkets, major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on LeonMarkets, IC3 for US claimants, state AG offices, off-ramp compliance, and civil-discovery overlay for high-value loss.