Reading the wallets — Phoenix casefile:

• Deposit confirmations from the claimant to Phoenix’s receiving wallet at phoenixapp.io.
• 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.

From the lectern — off-ramp identification:

• Phoenix off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The Phoenix off-ramp address is matched to known compliance feeds — the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for Phoenix — the packet meets the off-ramp’s published compliance standard.
• When the Phoenix off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Filing pathway — the next step after the off-ramp is identified:

1. Casefile triage on Phoenix — the submission is read; a written assessment is delivered.
2. Forensic trace on Phoenix — every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification — the Phoenix endpoint is named.
4. Recovery filing on Phoenix — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of Phoenix — the Professor follows the casefile until next-step documentation exists.

What we read in a Phoenix casefile:

• Chains the Professor reads for Phoenix casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in Phoenix — major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on Phoenix — IC3 for US claimants, state AG offices, off-ramp compliance, and civil-discovery overlay for high-value loss.

Boundaries on every Phoenix casefile — never crossed:

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