The annotation reads — wallet trace:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for Robotic Trade.
• 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.

From the lectern — off-ramp identification:

• Robotic 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 Robotic 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 Robotic Trade — the packet meets the off-ramp’s published compliance standard.
• When the Robotic Trade off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Filing pathway — the next step after the off-ramp is identified:

1. Read the Robotic Trade submission — written go/no-go returned.
2. Map the Robotic Trade wallet trail — every hop captured with chain-of-custody hashes.
3. Name the Robotic Trade off-ramp — endpoint counterparty identified.
4. Build and file the Robotic Trade recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the Robotic Trade file — until written next steps exist.

What the Professor tracks across Robotic Trade casefiles:

• Deposit + forwarding chains for Robotic Trade — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
• Off-ramps the Robotic Trade casefile may resolve to — centralised exchanges that respond to compliance filings.
• Filing pathways on Robotic Trade — IC3, state AG, off-ramp compliance, and civil-discovery overlay.

What the Professor will never do — by policy:

• On the Robotic Trade casefile — never request a seed phrase. Ever.
• On the Robotic Trade casefile — never request remote-access logins to a wallet or exchange.
• On the Robotic Trade casefile — never demand an upfront cash retainer to scope the matter.
• On the Robotic Trade casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the Robotic Trade casefile — never call the claimant unsolicited. Written-only.