On-chain reading, wallet flow for INCOGAIN:

• Deposit-side hashes from claimant wallets into INCOGAIN’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 map, where the funds left the chain:

• INCOGAIN casefiles end at a centralised exchange, Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for INCOGAIN is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for INCOGAIN, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the INCOGAIN casefile.

The Professor’s recovery note for INCOGAIN:

1. Casefile review on INCOGAIN, reading the submission against the no-go list.
2. Trace mapping on INCOGAIN, pathway documented to chain of custody standard.
3. Off-ramp naming on INCOGAIN, exchange endpoint identified.
4. Packet filing on INCOGAIN, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on INCOGAIN.

Chains and off-ramps the Professor follows:

• Chains tracked on INCOGAIN, 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 INCOGAIN, named exchange counterparties with public compliance contacts.
• Filings supported on INCOGAIN, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.