Reading the wallets, Chainblocks casefile:

• Deposit confirmations from the claimant to Chainblocks’s receiving wallet at chainbl0cks.net.
• 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.

The Professor’s off-ramp note:

• Off-ramp endpoint for Chainblocks resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Chainblocks’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Chainblocks is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the Chainblocks off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

The Professor’s recovery note for Chainblocks:

1. Submission triage, Chainblocks casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, Chainblocks deposit and forwarding wallets captured.
3. Endpoint identification, Chainblocks off-ramp wallet named.
4. Filing, Chainblocks packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, Chainblocks stays on file until a documented next step is reached.

What the casefile records, chains and counterparties:

• Chains in scope for Chainblocks, the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for Chainblocks, named centralised exchanges with compliance leverage.
• Filings supported on Chainblocks, IC3, state AG, off-ramp desk, civil discovery as applicable.