Off-ramp reading, exchange counterparty for Primus FX:

• Off-ramp endpoint for Primus FX resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Primus FX’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Primus FX is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the Primus FX off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

Recovery pathway, how this casefile moves toward filing:

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

What we read in a Primus FX casefile:

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