The annotation reads, wallet trace:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for OakleyVC.
• 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.

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

1. Triage on OakleyVC, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on OakleyVC, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on OakleyVC, off-ramp endpoint matched to a named exchange counterparty.
4. File the OakleyVC 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 OakleyVC, the Professor stays on the casefile until a documented next step exists.

Reading-list, chains and exchanges in scope:

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

Lines the Professor will not cross:

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