On-chain reading — wallet flow for Bitgerms:

• Deposit confirmations from the claimant to Bitgerms’s receiving wallet at bitgerms.com.
• Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
• Cross-chain bridge transactions where the operator routed value out of the deposit chain.
• Mixer or coin-join interactions, where applicable.
• Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

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

• Bitgerms casefiles end at a centralised exchange — Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for Bitgerms is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for Bitgerms — the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Bitgerms casefile.

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

1. Triage on Bitgerms — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on Bitgerms — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on Bitgerms — off-ramp endpoint matched to a named exchange counterparty.
4. File the Bitgerms packet — IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on Bitgerms — the Professor stays on the casefile until a documented next step exists.

What the on-chain reading covers:

• Deposit-side chains in Bitgerms 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 Bitgerms packets — centralised exchanges that accept regulator-grade compliance filings.
• Filing options on Bitgerms — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

What is never asked of a claimant:

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