Trace summary — funds that left bitopps.com:

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

Off-ramp reading — exchange counterparty for BitOpps:

• Off-ramp endpoint for BitOpps resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• BitOpps’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for BitOpps is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the BitOpps off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

Recovery pathway — how this casefile moves toward filing:

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

What we read in a BitOpps casefile:

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

Lines the Professor will not cross:

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