The annotation reads, wallet trace:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for Equitros.
• 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. Submission triage, Equitros casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, Equitros deposit and forwarding wallets captured.
3. Endpoint identification, Equitros off-ramp wallet named.
4. Filing, Equitros packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, Equitros stays on file until a documented next step is reached.

What the casefile records, chains and counterparties:

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

Boundaries on every Equitros casefile, never crossed:

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