The annotation reads, wallet trace:

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

How a iFinanceFX casefile becomes a evidence filing:

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

What the casefile records, chains and counterparties:

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

Boundaries on every iFinanceFX casefile, never crossed:

• What the Professor will not do on iFinanceFX, ask for a seed phrase.
• What the Professor will not do on iFinanceFX, request remote-access logins.
• What the Professor will not do on iFinanceFX, demand cash up front.
• What the Professor will not do on iFinanceFX, promise a guarantee.
• What the Professor will not do on iFinanceFX, call you out of the blue.