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

Category: Scam Brokers

Annotated readings of brokers and platforms the Cryptocurrency Professor has documented.

  • Casefile JB Drax Honoré — The Professor’s Note

    // FROM THE CASEFILE — JB DRAX HONORÉ

    When deposits to JB Drax Honoré via jbdh.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.

    Wallet trace — what the Professor maps:

    • Deposit confirmations from the claimant to JB Drax Honoré’s receiving wallet at jbdh.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 JB Drax Honoré:

    • Endpoint counterparty in the JB Drax Honoré casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • JB Drax Honoré’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
    • Leverage is applied to that named counterparty — the JB Drax Honoré packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the JB Drax Honoré off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

    The Professor’s recovery note for JB Drax Honoré:

    1. Read the JB Drax Honoré submission — written go/no-go returned.
    2. Map the JB Drax Honoré wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the JB Drax Honoré off-ramp — endpoint counterparty identified.
    4. Build and file the JB Drax Honoré recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the JB Drax Honoré file — until written next steps exist.

    What the on-chain reading covers:

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

    What the Professor will never do — by policy:

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

    Open a free consultation

    Open a free first consultation — /contact-us/ — written response within one business day.

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: Vecoglobal

    // FROM THE CASEFILE — VECOGLOBAL

    When deposits to Vecoglobal via vecoglobal.org 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.

    On-chain reading — wallet flow for Vecoglobal:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Vecoglobal.
    • 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.

    From the lectern — off-ramp identification:

    • Vecoglobal’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage — typically named in the packet alongside the deposit address.
    • Chain-analytics datasets cross-reference the Vecoglobal off-ramp wallet against historical laundering throughput.
    • The Vecoglobal packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for Vecoglobal, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

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

    1. Submission triage — Vecoglobal casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — Vecoglobal deposit and forwarding wallets captured.
    3. Endpoint identification — Vecoglobal off-ramp wallet named.
    4. Filing — Vecoglobal packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — Vecoglobal stays on file until a documented next step is reached.

    What the Professor tracks across Vecoglobal casefiles:

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

    Recovery scammers do these things; the Professor never does:

    • On the Vecoglobal casefile — never request a seed phrase. Ever.
    • On the Vecoglobal casefile — never request remote-access logins to a wallet or exchange.
    • On the Vecoglobal casefile — never demand an upfront cash retainer to scope the matter.
    • On the Vecoglobal casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the Vecoglobal 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 Fxcapitaltrade

    // FROM THE CASEFILE — FXCAPITALTRADE

    Funds you sent to Fxcapitaltrade (fxcapitaltrade.org) 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.

    Trace summary — funds that left fxcapitaltrade.org:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Fxcapitaltrade.
    • 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.

    Off-ramp reading — exchange counterparty for Fxcapitaltrade:

    • On the Fxcapitaltrade 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 Fxcapitaltrade is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the Fxcapitaltrade casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, Fxcapitaltrade escalates to IC3, state AG, and civil-discovery overlay.

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

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

    What the casefile records — chains and counterparties:

    • Chains the Fxcapitaltrade casefile may touch — Bitcoin and Ethereum at the deposit side, Tron USDT-TRC20 in stablecoin pathways, BNB Smart Chain and the L2s (Arbitrum, Optimism, Polygon, Base) where bridges link them.
    • Off-ramps relevant to Fxcapitaltrade — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the Fxcapitaltrade packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

    Boundaries on every Fxcapitaltrade casefile — never crossed:

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

    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: SDSTARFX

    // FROM THE CASEFILE — SDSTARFX

    The Professor opens the file on SDSTARFX 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.

    On-chain reading — wallet flow for SDSTARFX:

    • Claimant-to-platform deposit transactions on the deposit chain used by SDSTARFX.
    • 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.

    Off-ramp summary — SDSTARFX casefile:

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

    The Professor’s recovery note for SDSTARFX:

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

    Reading-list — chains and exchanges in scope:

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

    Boundaries on every SDSTARFX casefile — never crossed:

    • SDSTARFX policy — seed phrases are never requested.
    • SDSTARFX policy — remote-access logins are never requested.
    • SDSTARFX policy — no upfront cash retainer to scope.
    • SDSTARFX policy — no guaranteed-recovery language. None.
    • SDSTARFX policy — no unsolicited calls. The Professor responds in writing 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

  • Professor’s Brief: Bull Capital Trading Inc Ltd

    // FROM THE CASEFILE — BULL CAPITAL TRADING INC LTD

    Bull Capital Trading Inc Ltd is a casefile under reading. The deposits to bullcapitaltrading.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 Bull Capital Trading Inc Ltd:

    • Claimant-to-platform deposit transactions on the deposit chain used by Bull Capital Trading Inc Ltd.
    • 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.

    Off-ramp map — where the funds left the chain:

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

    Recovery pathway — how this casefile moves toward filing:

    1. Submission triage — Bull Capital Trading Inc Ltd casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — Bull Capital Trading Inc Ltd deposit and forwarding wallets captured.
    3. Endpoint identification — Bull Capital Trading Inc Ltd off-ramp wallet named.
    4. Filing — Bull Capital Trading Inc Ltd packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — Bull Capital Trading Inc Ltd stays on file until a documented next step is reached.

    Reading-list — chains and exchanges in scope:

    • Chains tracked on Bull Capital Trading Inc Ltd — 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 Bull Capital Trading Inc Ltd — named exchange counterparties with public compliance contacts.
    • Filings supported on Bull Capital Trading Inc Ltd — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile MTFE — The Professor’s Note

    // FROM THE CASEFILE — MTFE

    MTFE is a casefile under reading. The deposits to mtfe.ca 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:

    • Deposit transaction hashes from the claimant wallet to the MTFE 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 summary — MTFE casefile:

    • MTFE 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 MTFE is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for MTFE — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the MTFE casefile.

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

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

    Chains and off-ramps the Professor follows:

    • Chains the MTFE casefile may touch — Bitcoin and Ethereum at the deposit side, Tron USDT-TRC20 in stablecoin pathways, BNB Smart Chain and the L2s (Arbitrum, Optimism, Polygon, Base) where bridges link them.
    • Off-ramps relevant to MTFE — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the MTFE packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

    Lines the Professor will not cross:

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

    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

  • From the Lectern: ALLIANCE FX

    // FROM THE CASEFILE — ALLIANCE FX

    ALLIANCE FX, operating from alliancefx.net, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    From the marginalia — the deposit pathway:

    • Deposit-side hashes from claimant wallets into ALLIANCE FX’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 — ALLIANCE FX casefile:

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

    Chains and off-ramps the Professor follows:

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

    Lines the Professor will not cross:

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

    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

  • AIDI — Annotated by the Professor

    // FROM THE CASEFILE — AIDI

    Funds you sent to AIDI (aidifinancials.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 AIDI:

    • Claimant-to-platform deposit transactions on the deposit chain used by AIDI.
    • 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.

    Off-ramp reading — exchange counterparty for AIDI:

    • AIDI 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 AIDI is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for AIDI — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the AIDI casefile.

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

    1. Submission triage — AIDI casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — AIDI deposit and forwarding wallets captured.
    3. Endpoint identification — AIDI off-ramp wallet named.
    4. Filing — AIDI packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — AIDI stays on file until a documented next step is reached.

    What the casefile records — chains and counterparties:

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

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

    Open a free first consultation — /contact-us/ — written response within one business day.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Marverickfx — Annotated by the Professor

    // FROM THE CASEFILE — MARVERICKFX

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

    Trace summary — funds that left marverickfx.com:

    • Deposit transaction hashes from the claimant wallet to the Marverickfx 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 map — where the funds left the chain:

    • Endpoint counterparty in the Marverickfx casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Marverickfx’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
    • Leverage is applied to that named counterparty — the Marverickfx packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Marverickfx off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

    Recovery pathway — how this casefile moves toward filing:

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

    Chains and off-ramps the Professor follows:

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

    What is never asked of a claimant:

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

    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

  • Professor’s Brief: FX Russell

    // FROM THE CASEFILE — FX RUSSELL

    Funds you sent to FX Russell (russellgroupfxx.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.

    From the marginalia — the deposit pathway:

    • Deposit-side hashes from claimant wallets into FX Russell’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:

    • On the FX Russell 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 FX Russell is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the FX Russell casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, FX Russell escalates to IC3, state AG, and civil-discovery overlay.

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

    1. Triage on FX Russell — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on FX Russell — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on FX Russell — off-ramp endpoint matched to a named exchange counterparty.
    4. File the FX Russell packet — IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
    5. Follow-through on FX Russell — the Professor stays on the casefile until a documented next step exists.

    What the on-chain reading covers:

    • Chains the FX Russell casefile may touch — Bitcoin and Ethereum at the deposit side, Tron USDT-TRC20 in stablecoin pathways, BNB Smart Chain and the L2s (Arbitrum, Optimism, Polygon, Base) where bridges link them.
    • Off-ramps relevant to FX Russell — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the FX Russell packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

    Recovery scammers do these things; the Professor never does:

    • Boundary on FX Russell — seed phrases are off-limits.
    • Boundary on FX Russell — remote logins are off-limits.
    • Boundary on FX Russell — upfront cash retainers are off-limits.
    • Boundary on FX Russell — guaranteed-recovery promises are off-limits.
    • Boundary on FX Russell — unsolicited outbound contact is off-limits.

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace