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

• BitKingdom off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The BitKingdom 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 BitKingdom, the packet meets the off-ramp’s published compliance standard.
• When the BitKingdom off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

How a BitKingdom casefile becomes a evidence filing:

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

Chains and off-ramps the Professor follows:

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