The annotation continues, off-ramp endpoint:

• On the Well FX casefile, the off-ramp endpoint resolves to a centralised exchange, Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for Well FX is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the Well FX casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, Well FX escalates to IC3, state AG, and civil-discovery overlay.

How a Well FX casefile becomes a evidence filing:

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

What the casefile records, chains and counterparties:

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

Boundaries on every Well FX casefile, never crossed:

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