Trace summary, funds that left vortexgi.com:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for VortexGI.
• Forwarding wallets on the deposit chain, each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint, the centralised exchange deposit address holding the compliance lever.

Off-ramp map, where the funds left the chain:

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

Pathway to recovery, what happens after the trail is mapped:

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

What the on-chain reading covers:

• Chains the Professor reads for VortexGI casefiles, BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in VortexGI, major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on VortexGI, IC3 for US claimants, state AG offices, off-ramp compliance, and civil-discovery overlay for high-value loss.

Lines we never cross, by published policy:

• What the Professor will not do on VortexGI, ask for a seed phrase.
• What the Professor will not do on VortexGI, request remote-access logins.
• What the Professor will not do on VortexGI, demand cash up front.
• What the Professor will not do on VortexGI, promise a guarantee.
• What the Professor will not do on VortexGI, call you out of the blue.