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

• TEDX off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The TEDX off-ramp address is matched to known compliance feeds, the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for TEDX, the packet meets the off-ramp’s published compliance standard.
• When the TEDX off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

How a TEDX casefile becomes a evidence filing:

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

Reading-list, chains and exchanges in scope:

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

Boundaries on every TEDX casefile, never crossed:

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