Off-ramp summary, Connexar Capital casefile:

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

How a Connexar Capital casefile becomes a evidence filing:

1. Submission triage, Connexar Capital casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, Connexar Capital deposit and forwarding wallets captured.
3. Endpoint identification, Connexar Capital off-ramp wallet named.
4. Filing, Connexar Capital packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, Connexar Capital stays on file until a documented next step is reached.

Reading-list, chains and exchanges in scope:

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

Lines the Professor will not cross:

• What the Professor will not do on Connexar Capital, ask for a seed phrase.
• What the Professor will not do on Connexar Capital, request remote-access logins.
• What the Professor will not do on Connexar Capital, demand cash up front.
• What the Professor will not do on Connexar Capital, promise a guarantee.
• What the Professor will not do on Connexar Capital, call you out of the blue.