The annotation reads — wallet trace:

• Deposit transaction hashes from the claimant wallet to the HorizonFXPro platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

Off-ramp reading — exchange counterparty for HorizonFXPro:

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

Recovery pathway — how this casefile moves toward filing:

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

Reading-list — chains and exchanges in scope:

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

Lines we never cross — by published policy:

• HorizonFXPro policy — seed phrases are never requested.
• HorizonFXPro policy — remote-access logins are never requested.
• HorizonFXPro policy — no upfront cash retainer to scope.
• HorizonFXPro policy — no guaranteed-recovery language. None.
• HorizonFXPro policy — no unsolicited calls. The Professor responds in writing only.