Off-ramp summary, LitCrypto casefile:

• Off-ramp endpoint for LitCrypto resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• LitCrypto’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for LitCrypto is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the LitCrypto off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

Recovery pathway, how this casefile moves toward filing:

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

Reading-list, chains and exchanges in scope:

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