The annotation reads, wallet trace:

• Deposit-side hashes from claimant wallets into Sander FX’s receiving addresses.
• Operator forwarding wallets, deposit consolidation documented to chain of custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

The Professor’s off-ramp note:

• Sander FX 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 Sander FX is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for Sander FX, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Sander FX casefile.

Recovery pathway, how this casefile moves toward filing:

1. Triage on Sander FX, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on Sander FX, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on Sander FX, off-ramp endpoint matched to a named exchange counterparty.
4. File the Sander FX 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 Sander FX, the Professor stays on the casefile until a documented next step exists.

Boundaries on every Sander FX casefile, never crossed:

• Hard line on Sander FX, no seed-phrase requests, period.
• Hard line on Sander FX, no remote logins requested.
• Hard line on Sander FX, no upfront cash retainer.
• Hard line on Sander FX, no guarantee language.
• Hard line on Sander FX, no unsolicited phone outreach.