Reading the wallets — PrimeTverse casefile:

• Deposit confirmations from the claimant to PrimeTverse’s receiving wallet at primetverse.net.
• Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
• Cross-chain bridge transactions where the operator routed value out of the deposit chain.
• Mixer or coin-join interactions, where applicable.
• Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

Off-ramp reading — exchange counterparty for PrimeTverse:

• Endpoint counterparty in the PrimeTverse casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• PrimeTverse’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty — the PrimeTverse packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the PrimeTverse off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

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

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

Reading-list — chains and exchanges in scope:

• Chains in scope for PrimeTverse — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for PrimeTverse — named centralised exchanges with compliance leverage.
• Filings supported on PrimeTverse — IC3, state AG, off-ramp desk, civil discovery as applicable.

What the Professor will never do — by policy:

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