From the marginalia, the deposit pathway:

• Initial deposit hashes to the Vannit Bit receiving address at vannitbit.com.
• Hop-by-hop forwarding wallets across the deposit chain, captured with chain of custody hashes.
• Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
• Obfuscation events through mixer contracts and privacy services.
• Centralised-exchange off-ramp wallets, the named counterparty that holds compliance leverage.

Off-ramp summary, Vannit Bit casefile:

• Vannit Bit’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 Vannit Bit off-ramp wallet against historical laundering throughput.
• The Vannit Bit packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for Vannit Bit, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

Recovery pathway, how this casefile moves toward filing:

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

What the casefile records, chains and counterparties:

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