On-chain reading, wallet flow for FTC:

• Deposit-side hashes from claimant wallets into FTC’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.

Off-ramp reading, exchange counterparty for FTC:

• Off-ramp endpoint for FTC resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• FTC’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for FTC is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the FTC off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

The Professor’s recovery note for FTC:

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

Chains and off-ramps the Professor follows:

• Chains the FTC 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 FTC, the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the FTC packet supports, IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.