On-chain reading, wallet flow for DAILY TRADE:

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

The Professor’s recovery note for DAILY TRADE:

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

Reading-list, chains and exchanges in scope:

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

Boundaries on every DAILY TRADE casefile, never crossed:

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