On-chain reading, wallet flow for AIFundBTC:

• Deposit-side hashes from claimant wallets into AIFundBTC’s receiving addresses.
• Operator forwarding wallets, deposit consolidation documented to chain of custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

The Professor’s off-ramp note:

• AIFundBTC’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 AIFundBTC off-ramp wallet against historical laundering throughput.
• The AIFundBTC packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for AIFundBTC, 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. Casefile review on AIFundBTC, reading the submission against the no-go list.
2. Trace mapping on AIFundBTC, pathway documented to chain of custody standard.
3. Off-ramp naming on AIFundBTC, exchange endpoint identified.
4. Packet filing on AIFundBTC, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on AIFundBTC.

Chains and off-ramps the Professor follows:

• Chains the AIFundBTC casefile may touch, Bitcoin and Ethereum at the deposit side, Tron USDT-TRC20 in stablecoin pathways, BNB Smart Chain and the L2s (Arbitrum, Optimism, Polygon, Base) where bridges link them.
• Off-ramps relevant to AIFundBTC, the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the AIFundBTC packet supports, IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.