On-chain reading, wallet flow for IBTP:

• Deposit-side hashes from claimant wallets into IBTP’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.

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

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

What the casefile records, chains and counterparties:

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

Lines the Professor will not cross:

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