The Professor’s off-ramp note:

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

Recovery sequence, from on-chain reading to filed packet:

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

What the casefile records, chains and counterparties:

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