Recovery Doctrine: chain-of-custody · verifiable on-chain trail · regulator-ready packets verification chain: Etherscan · SlowMist · CertiK
45 claims under active investigation 92 wallet routes mapped this month Open a Free Recovery Consultation →

Tag: scam broker

  • Professor’s Brief: OliveCryptoTrading

    // FROM THE CASEFILE — OLIVECRYPTOTRADING

    OliveCryptoTrading is a casefile under reading. The deposits to olivecryptotrading.com sit on-chain, immutable; the wallet pathway is the primary source, and the off-ramp endpoint is the conclusion the Professor’s marginalia points toward.

    The annotation reads — wallet trace:

    • Initial deposit hashes to the OliveCryptoTrading receiving address at olivecryptotrading.com.
    • Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
    • Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
    • Obfuscation events through mixer contracts and privacy services.
    • Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

    Off-ramp summary — OliveCryptoTrading casefile:

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

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

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

    Chains and off-ramps the Professor follows:

    • Deposit-side chains in OliveCryptoTrading casefiles — typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT) — with bridge crossings noted.
    • Off-ramps named in OliveCryptoTrading packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on OliveCryptoTrading — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

    Send the wallet for trace — /submit-a-case/ — the Professor responds in writing.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: Esplanade

    // FROM THE CASEFILE — ESPLANADE

    The Professor opens the file on Esplanade the same way every casefile is opened — by treating the wallet history as text and the off-ramp endpoint as the citation a regulator can verify.

    Trace summary — funds that left esplanade-ms.com:

    • Deposit confirmations from the claimant to Esplanade’s receiving wallet at esplanade-ms.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 summary — Esplanade casefile:

    • Esplanade casefiles end at a centralised exchange — Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
    • Off-ramp wallet for Esplanade is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for Esplanade — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Esplanade casefile.

    How a Esplanade casefile becomes a regulator-ready filing:

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

    What the casefile records — chains and counterparties:

    • Deposit + forwarding chains for Esplanade — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
    • Off-ramps the Esplanade casefile may resolve to — centralised exchanges that respond to compliance filings.
    • Filing pathways on Esplanade — IC3, state AG, off-ramp compliance, and civil-discovery overlay.

    Lines the Professor will not cross:

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

    Open a free consultation

    Book a reading of your wallet — file at /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Kasper Capital Markets

    // FROM THE CASEFILE — KASPER CAPITAL MARKETS

    When deposits to Kasper Capital Markets via kasperfx.com go quiet, the on-chain record stays loud. The Professor’s reading begins where the platform’s silence does — with the wallet that received the funds and the path it took afterward.

    Reading the wallets — Kasper Capital Markets casefile:

    • Claimant-to-platform deposit transactions on the deposit chain used by Kasper Capital Markets.
    • Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
    • Cross-chain bridge events to chains with deeper exchange liquidity.
    • Privacy-service interactions, where present in the trail.
    • Off-ramp wallet — the named centralised-exchange endpoint.

    The Professor’s off-ramp note:

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

    The Professor’s recovery note for Kasper Capital Markets:

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

    What the Professor tracks across Kasper Capital Markets casefiles:

    • Deposit + forwarding chains for Kasper Capital Markets — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
    • Off-ramps the Kasper Capital Markets casefile may resolve to — centralised exchanges that respond to compliance filings.
    • Filing pathways on Kasper Capital Markets — IC3, state AG, off-ramp compliance, and civil-discovery overlay.

    What is never asked of a claimant:

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

    Open a free consultation

    Submit your wallet for a forensic reading — /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Bit Markets — The Professor’s Note

    // FROM THE CASEFILE — BIT MARKETS

    When a deposit ledgered to Bit Markets at bitmarkets.ca stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    From the marginalia — the deposit pathway:

    • Deposit-side hashes from claimant wallets into Bit Markets’s receiving addresses.
    • Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
    • Inter-chain bridge transactions when value moves toward off-ramp liquidity.
    • Mixer/obfuscation events the operator routed through, where present.
    • Final off-ramp endpoint and named counterparty exchange.

    Off-ramp summary — Bit Markets casefile:

    • On the Bit Markets casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
    • The off-ramp wallet for Bit Markets is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the Bit Markets casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, Bit Markets escalates to IC3, state AG, and civil-discovery overlay.

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

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

    What the casefile records — chains and counterparties:

    • Deposit-side chains in Bit Markets casefiles — typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT) — with bridge crossings noted.
    • Off-ramps named in Bit Markets packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Bit Markets — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    What is never asked of a claimant:

    • Recovery scammers do these things on Bit Markets; the Professor never does — request seed phrases.
    • Recovery scammers do these things on Bit Markets; the Professor never does — request remote logins.
    • Recovery scammers do these things on Bit Markets; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on Bit Markets; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on Bit Markets; the Professor never does — call you unsolicited.

    Open a free consultation

    Send the wallet for trace — /submit-a-case/ — the Professor responds in writing.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: FinInsider

    // FROM THE CASEFILE — FININSIDER

    Funds you sent to FinInsider (fininsider.ai) are still recorded on the public ledger; the question is no longer whether the money moved but where the off-ramp opened — and that is what the Professor reads.

    From the marginalia — the deposit pathway:

    • Deposit-side hashes from claimant wallets into FinInsider’s receiving addresses.
    • Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
    • Inter-chain bridge transactions when value moves toward off-ramp liquidity.
    • Mixer/obfuscation events the operator routed through, where present.
    • Final off-ramp endpoint and named counterparty exchange.

    The annotation continues — off-ramp endpoint:

    • FinInsider casefiles end at a centralised exchange — Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
    • Off-ramp wallet for FinInsider is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for FinInsider — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the FinInsider casefile.

    Pathway to recovery — what happens after the trail is mapped:

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

    Reading-list — chains and exchanges in scope:

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

    What is never asked of a claimant:

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

    Open a free consultation

    Submit your wallet for a forensic reading — /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Fake Zijing Capital — The Professor’s Note

    // FROM THE CASEFILE — FAKE ZIJING CAPITAL

    Fake Zijing Capital is a casefile under reading. The deposits to zjcapital-hk.com sit on-chain, immutable; the wallet pathway is the primary source, and the off-ramp endpoint is the conclusion the Professor’s marginalia points toward.

    On-chain reading — wallet flow for Fake Zijing Capital:

    • Deposit transaction hashes from the claimant wallet to the Fake Zijing Capital platform receiving address.
    • Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
    • Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
    • Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
    • Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

    The Professor’s off-ramp note:

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

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

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

    What the on-chain reading covers:

    • Chains tracked on Fake Zijing Capital — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
    • Off-ramps tracked on Fake Zijing Capital — named exchange counterparties with public compliance contacts.
    • Filings supported on Fake Zijing Capital — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

    Boundaries on every Fake Zijing Capital casefile — never crossed:

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

    Open a free consultation

    Submit your wallet for a forensic reading — /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Crypto Elit Fx

    // FROM THE CASEFILE — CRYPTO ELIT FX

    When deposits to Crypto Elit Fx via cryptoelitfx.com go quiet, the on-chain record stays loud. The Professor’s reading begins where the platform’s silence does — with the wallet that received the funds and the path it took afterward.

    Trace summary — funds that left cryptoelitfx.com:

    • Deposit confirmations from the claimant to Crypto Elit Fx’s receiving wallet at cryptoelitfx.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 Crypto Elit Fx:

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

    Pathway to recovery — what happens after the trail is mapped:

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

    What we read in a Crypto Elit Fx casefile:

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

    Boundaries on every Crypto Elit Fx casefile — never crossed:

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

    Open a free consultation

    Bring the casefile to office hours — open a free consultation at /contact-us/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Professor’s Brief: FXNOBEL

    // FROM THE CASEFILE — FXNOBEL

    FXNOBEL, operating from fxnobel.com, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    Reading the wallets — FXNOBEL casefile:

    • Deposit transaction hashes from the claimant wallet to the FXNOBEL platform receiving address.
    • Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
    • Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
    • Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
    • Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

    The annotation continues — off-ramp endpoint:

    • Off-ramp endpoint for FXNOBEL resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • FXNOBEL’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for FXNOBEL is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the FXNOBEL 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. Submission triage — FXNOBEL casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — FXNOBEL deposit and forwarding wallets captured.
    3. Endpoint identification — FXNOBEL off-ramp wallet named.
    4. Filing — FXNOBEL packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — FXNOBEL stays on file until a documented next step is reached.

    What the casefile records — chains and counterparties:

    • Chains tracked on FXNOBEL — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
    • Off-ramps tracked on FXNOBEL — named exchange counterparties with public compliance contacts.
    • Filings supported on FXNOBEL — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

    What is never asked of a claimant:

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

    Open a free consultation

    The Professor reads claims at no charge to begin — open a consultation at /contact-us/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: Discovery FX

    // FROM THE CASEFILE — DISCOVERY FX

    Funds you sent to Discovery FX (discovery-forex.com) are still recorded on the public ledger; the question is no longer whether the money moved but where the off-ramp opened — and that is what the Professor reads.

    On-chain reading — wallet flow for Discovery FX:

    • Deposit transaction hashes from the claimant wallet to the Discovery FX platform receiving address.
    • Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
    • Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
    • Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
    • Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

    Off-ramp reading — exchange counterparty for Discovery FX:

    • Discovery FX off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Discovery FX 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 Discovery FX — the packet meets the off-ramp’s published compliance standard.
    • When the Discovery FX off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

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

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

    What the Professor tracks across Discovery FX casefiles:

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

    What the Professor will never do — by policy:

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

    Open a free consultation

    Submit your wallet for a forensic reading — /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace