The annotation reads, wallet trace:

• Deposit transaction hashes from the claimant wallet to the AES 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.

Off-ramp reading, exchange counterparty for AES:

• On the AES 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 AES is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the AES casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, AES escalates to IC3, state AG, and civil-discovery overlay.

The Professor’s recovery note for AES:

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

Lines the Professor will not cross:

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