The annotation reads, wallet trace:

• Deposit transaction hashes from the claimant wallet to the Nexymus platform receiving address.
• Forwarding wallets the platform consolidated through, typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions, Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet, the centralised exchange deposit address that received the consolidated funds.

How a Nexymus casefile becomes a evidence filing:

1. Casefile review on Nexymus, reading the submission against the no-go list.
2. Trace mapping on Nexymus, pathway documented to chain of custody standard.
3. Off-ramp naming on Nexymus, exchange endpoint identified.
4. Packet filing on Nexymus, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on Nexymus.

Reading-list, chains and exchanges in scope:

• Chains the Professor reads for Nexymus casefiles, BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in Nexymus, major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on Nexymus, IC3 for US claimants, state AG offices, off-ramp compliance, and civil-discovery overlay for high-value loss.

Boundaries on every Nexymus casefile, never crossed:

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