Trace summary, funds that left chainpilot.co:

• Initial deposit hashes to the Chainpilot receiving address at chainpilot.co.
• Hop-by-hop forwarding wallets across the deposit chain, captured with chain of custody hashes.
• Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
• Obfuscation events through mixer contracts and privacy services.
• Centralised-exchange off-ramp wallets, the named counterparty that holds compliance leverage.

Off-ramp reading, exchange counterparty for Chainpilot:

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

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

1. First read on Chainpilot, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on Chainpilot, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for Chainpilot is named to a centralised exchange wallet.
4. Packet filing on Chainpilot, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with Chainpilot until a documented outcome or escalation step is on file.

What we read in a Chainpilot casefile:

• Chains tracked on Chainpilot, Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on Chainpilot, named exchange counterparties with public compliance contacts.
• Filings supported on Chainpilot, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.

Lines the Professor will not cross:

• On the Chainpilot casefile, never request a seed phrase. Ever.
• On the Chainpilot casefile, never request remote-access logins to a wallet or exchange.
• On the Chainpilot casefile, never demand an upfront cash retainer to scope the matter.
• On the Chainpilot casefile, never promise a guaranteed recovery. The trail does not promise one.
• On the Chainpilot casefile, never call the claimant unsolicited. Written-only.