Trace summary — funds that left bitcoins-code.de:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for Bitcoin Code.
• Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

The annotation continues — off-ramp endpoint:

• Bitcoin Code off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The Bitcoin Code off-ramp address is matched to known compliance feeds — the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for Bitcoin Code — the packet meets the off-ramp’s published compliance standard.
• When the Bitcoin Code off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Recovery pathway — how this casefile moves toward filing:

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

Chains and off-ramps the Professor follows:

• Deposit-side chains in Bitcoin Code casefiles — typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT) — with bridge crossings noted.
• Off-ramps named in Bitcoin Code packets — centralised exchanges that accept regulator-grade compliance filings.
• Filing options on Bitcoin Code — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

What the Professor will never do — by policy:

• Hard line on Bitcoin Code — no seed-phrase requests, period.
• Hard line on Bitcoin Code — no remote logins requested.
• Hard line on Bitcoin Code — no upfront cash retainer.
• Hard line on Bitcoin Code — no guarantee language.
• Hard line on Bitcoin Code — no unsolicited phone outreach.