Wallet trace — what the Professor maps:

• Deposit-side hashes from claimant wallets into Bake’s receiving addresses.
• Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

From the lectern — off-ramp identification:

• Bake’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage — typically named in the packet alongside the deposit address.
• Chain-analytics datasets cross-reference the Bake off-ramp wallet against historical laundering throughput.
• The Bake packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for Bake, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

Recovery sequence — from on-chain reading to filed packet:

1. Casefile triage on Bake — the submission is read; a written assessment is delivered.
2. Forensic trace on Bake — every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification — the Bake endpoint is named.
4. Recovery filing on Bake — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of Bake — the Professor follows the casefile until next-step documentation exists.

What the on-chain reading covers:

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

What is never asked of a claimant:

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