Reading the wallets, OrbisFX casefile:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for OrbisFX.
• Forwarding wallets on the deposit chain, each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint, the centralised exchange deposit address holding the compliance lever.

The Professor’s recovery note for OrbisFX:

1. First read on OrbisFX, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on OrbisFX, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for OrbisFX is named to a centralised exchange wallet.
4. Packet filing on OrbisFX, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with OrbisFX until a documented outcome or escalation step is on file.

What the Professor will never do, by policy:

• Hard line on OrbisFX, no seed-phrase requests, period.
• Hard line on OrbisFX, no remote logins requested.
• Hard line on OrbisFX, no upfront cash retainer.
• Hard line on OrbisFX, no guarantee language.
• Hard line on OrbisFX, no unsolicited phone outreach.