From the marginalia, the deposit pathway:

• Claimant-to-platform deposit transactions on the deposit chain used by Imax Point Market.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet, the named centralised-exchange endpoint.

The annotation continues, off-ramp endpoint:

• Off-ramp endpoint for Imax Point Market resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Imax Point Market’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Imax Point Market is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the Imax Point Market 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 Imax Point Market submission, written go/no-go returned.
2. Map the Imax Point Market wallet trail, every hop captured with chain of custody hashes.
3. Name the Imax Point Market off-ramp, endpoint counterparty identified.
4. Build and file the Imax Point Market recovery packet, to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the Imax Point Market file, until written next steps exist.

What the Professor will never do, by policy:

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