The annotation reads, wallet trace:

• Initial deposit hashes to the WadTrade receiving address at wadtrade.com.
• Hop-by-hop forwarding wallets across the deposit chain, captured with chain of custody hashes.
• Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
• Obfuscation events through mixer contracts and privacy services.
• Centralised-exchange off-ramp wallets, the named counterparty that holds compliance leverage.

Off-ramp map, where the funds left the chain:

• WadTrade off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The WadTrade 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 WadTrade, the packet meets the off-ramp’s published compliance standard.
• When the WadTrade off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

How a WadTrade casefile becomes a evidence filing:

1. Submission triage, WadTrade casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, WadTrade deposit and forwarding wallets captured.
3. Endpoint identification, WadTrade off-ramp wallet named.
4. Filing, WadTrade packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, WadTrade stays on file until a documented next step is reached.

What the Professor will never do, by policy:

• Hard line on WadTrade, no seed-phrase requests, period.
• Hard line on WadTrade, no remote logins requested.
• Hard line on WadTrade, no upfront cash retainer.
• Hard line on WadTrade, no guarantee language.
• Hard line on WadTrade, no unsolicited phone outreach.