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

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

How a AezaTrade casefile becomes a evidence filing:

1. Triage on AezaTrade, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on AezaTrade, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on AezaTrade, off-ramp endpoint matched to a named exchange counterparty.
4. File the AezaTrade packet, IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on AezaTrade, the Professor stays on the casefile until a documented next step exists.

Chains and off-ramps the Professor follows:

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

What the Professor will never do, by policy:

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