The annotation reads, wallet trace:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for FinvestAI.
• 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 annotation continues, off-ramp endpoint:

• FinvestAI’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage, typically named in the packet alongside the deposit address.
• Chain-analytics datasets cross-reference the FinvestAI off-ramp wallet against historical laundering throughput.
• The FinvestAI packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for FinvestAI, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

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

1. Submission triage, FinvestAI casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, FinvestAI deposit and forwarding wallets captured.
3. Endpoint identification, FinvestAI off-ramp wallet named.
4. Filing, FinvestAI packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, FinvestAI stays on file until a documented next step is reached.