Wallet trace — what the Professor maps:

• Deposit confirmations from the claimant to LUNEX CLOUD’s receiving wallet at lunexcloud.com.
• 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.

The Professor’s off-ramp note:

• LUNEX CLOUD off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The LUNEX CLOUD 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 LUNEX CLOUD — the packet meets the off-ramp’s published compliance standard.
• When the LUNEX CLOUD 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 review on LUNEX CLOUD — reading the submission against the no-go list.
2. Trace mapping on LUNEX CLOUD — pathway documented to chain-of-custody standard.
3. Off-ramp naming on LUNEX CLOUD — exchange endpoint identified.
4. Packet filing on LUNEX CLOUD — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on LUNEX CLOUD.

Reading-list — chains and exchanges in scope:

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

What the Professor will never do — by policy:

• LUNEX CLOUD policy — seed phrases are never requested.
• LUNEX CLOUD policy — remote-access logins are never requested.
• LUNEX CLOUD policy — no upfront cash retainer to scope.
• LUNEX CLOUD policy — no guaranteed-recovery language. None.
• LUNEX CLOUD policy — no unsolicited calls. The Professor responds in writing only.