The Professor’s off-ramp note:

• Off-ramp endpoint for EXolid resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• EXolid’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for EXolid is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the EXolid 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. First read on EXolid, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on EXolid, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for EXolid is named to a centralised exchange wallet.
4. Packet filing on EXolid, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with EXolid until a documented outcome or escalation step is on file.

What the casefile records, chains and counterparties:

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

Boundaries on every EXolid casefile, never crossed:

• EXolid policy, seed phrases are never requested.
• EXolid policy, remote-access logins are never requested.
• EXolid policy, no upfront cash retainer to scope.
• EXolid policy, no guaranteed-recovery language. None.
• EXolid policy, no unsolicited calls. The Professor responds in writing only.