The annotation reads, wallet trace:

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

The annotation continues, off-ramp endpoint:

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

Recovery pathway, how this casefile moves toward filing:

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

Boundaries on every ESPERIO casefile, never crossed:

• ESPERIO policy, seed phrases are never requested.
• ESPERIO policy, remote-access logins are never requested.
• ESPERIO policy, no upfront cash retainer to scope.
• ESPERIO policy, no guaranteed-recovery language. None.
• ESPERIO policy, no unsolicited calls. The Professor responds in writing only.