Trace summary — funds that left kryptod.com:

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

Filing pathway — the next step after the off-ramp is identified:

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

Reading-list — chains and exchanges in scope:

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

Boundaries on every Kryptod casefile — never crossed:

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