Off-ramp summary, XM Defi casefile:

• Off-ramp endpoint for XM Defi resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• XM Defi’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for XM Defi is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the XM Defi 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 XM Defi, the submission is read; a written assessment is delivered.
2. Forensic trace on XM Defi, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the XM Defi endpoint is named.
4. Recovery filing on XM Defi, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of XM Defi, the Professor follows the casefile until next-step documentation exists.

What the casefile records, chains and counterparties:

• Chains tracked on XM Defi, Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on XM Defi, named exchange counterparties with public compliance contacts.
• Filings supported on XM Defi, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.