Reading the wallets, QIVIUT casefile:

• Initial deposit hashes to the QIVIUT receiving address at qclfx.co.
• 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 map, where the funds left the chain:

• On the QIVIUT casefile, the off-ramp endpoint resolves to a centralised exchange, Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for QIVIUT is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the QIVIUT casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, QIVIUT escalates to IC3, state AG, and civil-discovery overlay.

How a QIVIUT casefile becomes a evidence filing:

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

Reading-list, chains and exchanges in scope:

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