The annotation reads, wallet trace:

• Claimant-to-platform deposit transactions on the deposit chain used by Nexus Trade.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet, the named centralised-exchange endpoint.

The annotation continues, off-ramp endpoint:

• Nexus Trade off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The Nexus Trade off-ramp address is matched to known compliance feeds, the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for Nexus Trade, the packet meets the off-ramp’s published compliance standard.
• When the Nexus Trade off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Recovery pathway, how this casefile moves toward filing:

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