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

• Endpoint counterparty in the Yondaris casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Yondaris’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty, the Yondaris packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Yondaris off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

The Professor’s recovery note for Yondaris:

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

Boundaries on every Yondaris casefile, never crossed:

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