Off-ramp reading, exchange counterparty for FX CTRUM:

• FX CTRUM off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The FX CTRUM 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 FX CTRUM, the packet meets the off-ramp’s published compliance standard.
• When the FX CTRUM 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. Casefile review on FX CTRUM, reading the submission against the no-go list.
2. Trace mapping on FX CTRUM, pathway documented to chain of custody standard.
3. Off-ramp naming on FX CTRUM, exchange endpoint identified.
4. Packet filing on FX CTRUM, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on FX CTRUM.

What the casefile records, chains and counterparties:

• Deposit + forwarding chains for FX CTRUM, Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
• Off-ramps the FX CTRUM casefile may resolve to, centralised exchanges that respond to compliance filings.
• Filing pathways on FX CTRUM, IC3, state AG, off-ramp compliance, and civil-discovery overlay.