The annotation reads — wallet trace:

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

The annotation continues — off-ramp endpoint:

• Endpoint counterparty in the EFGH casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• EFGH’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 EFGH packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the EFGH 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.

How a EFGH casefile becomes a regulator-ready filing:

1. Read the EFGH submission — written go/no-go returned.
2. Map the EFGH wallet trail — every hop captured with chain-of-custody hashes.
3. Name the EFGH off-ramp — endpoint counterparty identified.
4. Build and file the EFGH recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the EFGH file — until written next steps exist.

What the casefile records — chains and counterparties:

• Chains tracked on EFGH — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on EFGH — named exchange counterparties with public compliance contacts.
• Filings supported on EFGH — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

Lines we never cross — by published policy:

• On the EFGH casefile — never request a seed phrase. Ever.
• On the EFGH casefile — never request remote-access logins to a wallet or exchange.
• On the EFGH casefile — never demand an upfront cash retainer to scope the matter.
• On the EFGH casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the EFGH casefile — never call the claimant unsolicited. Written-only.