From the marginalia, the deposit pathway:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for SyosSpace.
• Forwarding wallets on the deposit chain, each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint, the centralised exchange deposit address holding the compliance lever.

The Professor’s off-ramp note:

• SyosSpace’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage, typically named in the packet alongside the deposit address.
• Chain-analytics datasets cross-reference the SyosSpace off-ramp wallet against historical laundering throughput.
• The SyosSpace packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for SyosSpace, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

Recovery pathway, how this casefile moves toward filing:

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