The annotation reads, wallet trace:

• Initial deposit hashes to the IGB Markets receiving address at igbmarkets.com.
• 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.

The annotation continues, off-ramp endpoint:

• IGB Markets 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 IGB Markets is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for IGB Markets, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the IGB Markets casefile.

Recovery sequence, from on-chain reading to filed packet:

1. Submission triage, IGB Markets casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, IGB Markets deposit and forwarding wallets captured.
3. Endpoint identification, IGB Markets off-ramp wallet named.
4. Filing, IGB Markets packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, IGB Markets stays on file until a documented next step is reached.

Lines the Professor will not cross:

• On the IGB Markets casefile, never request a seed phrase. Ever.
• On the IGB Markets casefile, never request remote-access logins to a wallet or exchange.
• On the IGB Markets casefile, never demand an upfront cash retainer to scope the matter.
• On the IGB Markets casefile, never promise a guaranteed recovery. The trail does not promise one.
• On the IGB Markets casefile, never call the claimant unsolicited. Written-only.