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

• Off-ramp endpoint for Morgantrust resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Morgantrust’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Morgantrust is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the Morgantrust off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

How a Morgantrust casefile becomes a evidence filing:

1. First read on Morgantrust, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on Morgantrust, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for Morgantrust is named to a centralised exchange wallet.
4. Packet filing on Morgantrust, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with Morgantrust until a documented outcome or escalation step is on file.

Chains and off-ramps the Professor follows:

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