Wallet trace — what the Professor maps:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for Fintevex.
• 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 summary — Fintevex casefile:

• Endpoint counterparty in the Fintevex casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Fintevex’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty — the Fintevex packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Fintevex off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

Filing pathway — the next step after the off-ramp is identified:

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

What the on-chain reading covers:

• Deposit + forwarding chains for Fintevex — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
• Off-ramps the Fintevex casefile may resolve to — centralised exchanges that respond to compliance filings.
• Filing pathways on Fintevex — IC3, state AG, off-ramp compliance, and civil-discovery overlay.

Lines we never cross — by published policy:

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