The annotation continues, off-ramp endpoint:

• FXBoxed casefiles end at a centralised exchange, Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for FXBoxed is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for FXBoxed, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the FXBoxed casefile.

How a FXBoxed casefile becomes a evidence filing:

1. Triage on FXBoxed, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on FXBoxed, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on FXBoxed, off-ramp endpoint matched to a named exchange counterparty.
4. File the FXBoxed packet, IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on FXBoxed, the Professor stays on the casefile until a documented next step exists.

What the Professor will never do, by policy:

• On the FXBoxed casefile, never request a seed phrase. Ever.
• On the FXBoxed casefile, never request remote-access logins to a wallet or exchange.
• On the FXBoxed casefile, never demand an upfront cash retainer to scope the matter.
• On the FXBoxed casefile, never promise a guaranteed recovery. The trail does not promise one.
• On the FXBoxed casefile, never call the claimant unsolicited. Written-only.