The annotation reads, wallet trace:

• Claimant-to-platform deposit transactions on the deposit chain used by Deuxstock.
• 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.

Off-ramp reading, exchange counterparty for Deuxstock:

• On the Deuxstock casefile, the off-ramp endpoint resolves to a centralised exchange, Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for Deuxstock is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the Deuxstock casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, Deuxstock escalates to IC3, state AG, and civil-discovery overlay.

Recovery sequence, from on-chain reading to filed packet:

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

Boundaries on every Deuxstock casefile, never crossed:

• Boundary on Deuxstock, seed phrases are off-limits.
• Boundary on Deuxstock, remote logins are off-limits.
• Boundary on Deuxstock, upfront cash retainers are off-limits.
• Boundary on Deuxstock, guaranteed-recovery promises are off-limits.
• Boundary on Deuxstock, unsolicited outbound contact is off-limits.