The annotation reads, wallet trace:

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

How a MTFXG casefile becomes a evidence filing:

1. Triage on MTFXG, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on MTFXG, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on MTFXG, off-ramp endpoint matched to a named exchange counterparty.
4. File the MTFXG packet, IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on MTFXG, the Professor stays on the casefile until a documented next step exists.

What the casefile records, chains and counterparties:

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