Off-ramp reading, exchange counterparty for LunarPips:

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

Recovery sequence, from on-chain reading to filed packet:

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

Reading-list, chains and exchanges in scope:

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

Boundaries on every LunarPips casefile, never crossed:

• What the Professor will not do on LunarPips, ask for a seed phrase.
• What the Professor will not do on LunarPips, request remote-access logins.
• What the Professor will not do on LunarPips, demand cash up front.
• What the Professor will not do on LunarPips, promise a guarantee.
• What the Professor will not do on LunarPips, call you out of the blue.