The annotation continues, off-ramp endpoint:

• MarFx casefiles end at a centralised exchange, Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for MarFx is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for MarFx, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the MarFx casefile.

The Professor’s recovery note for MarFx:

1. Submission triage, MarFx casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, MarFx deposit and forwarding wallets captured.
3. Endpoint identification, MarFx off-ramp wallet named.
4. Filing, MarFx packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, MarFx stays on file until a documented next step is reached.

What we read in a MarFx casefile:

• Chains tracked on MarFx, Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on MarFx, named exchange counterparties with public compliance contacts.
• Filings supported on MarFx, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.

Boundaries on every MarFx casefile, never crossed:

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