The annotation reads, wallet trace:

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

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

Recovery pathway, how this casefile moves toward filing:

1. Casefile triage on Dynamiq Markets, the submission is read; a written assessment is delivered.
2. Forensic trace on Dynamiq Markets, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the Dynamiq Markets endpoint is named.
4. Recovery filing on Dynamiq Markets, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of Dynamiq Markets, the Professor follows the casefile until next-step documentation exists.

Boundaries on every Dynamiq Markets casefile, never crossed:

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