Reading the wallets, Rubik Trade casefile:

• Deposit confirmations from the claimant to Rubik Trade’s receiving wallet at rubiktrade.com.
• Forwarding-wallet pathway documented hop-by-hop with chain of custody hashes.
• Cross-chain bridge transactions where the operator routed value out of the deposit chain.
• Mixer or coin-join interactions, where applicable.
• Final off-ramp at a centralised exchange, the compliance counterparty named in the recovery filing.

The Professor’s off-ramp note:

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

How a Rubik Trade casefile becomes a evidence filing:

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

Reading-list, chains and exchanges in scope:

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