Wallet trace — what the Professor maps:

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

From the lectern — off-ramp identification:

• MetaChainFx’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage — typically named in the packet alongside the deposit address.
• Chain-analytics datasets cross-reference the MetaChainFx off-ramp wallet against historical laundering throughput.
• The MetaChainFx packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for MetaChainFx, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

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

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

What the casefile records — chains and counterparties:

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

Boundaries on every MetaChainFx casefile — never crossed:

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