Reading the wallets, Kana Capitals casefile:

• Deposit transaction hashes from the claimant wallet to the Kana Capitals platform receiving address.
• Forwarding wallets the platform consolidated through, typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions, Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet, the centralised exchange deposit address that received the consolidated funds.

Recovery pathway, how this casefile moves toward filing:

1. Read the Kana Capitals submission, written go/no-go returned.
2. Map the Kana Capitals wallet trail, every hop captured with chain of custody hashes.
3. Name the Kana Capitals off-ramp, endpoint counterparty identified.
4. Build and file the Kana Capitals recovery packet, to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the Kana Capitals file, until written next steps exist.

What the casefile records, chains and counterparties:

• Chains tracked on Kana Capitals, Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on Kana Capitals, named exchange counterparties with public compliance contacts.
• Filings supported on Kana Capitals, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.