Recovery Doctrine: chain-of-custody · verifiable on-chain trail · regulator-ready packets verification chain: Etherscan · SlowMist · CertiK
40 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.

  • bitqy — Annotated by the Professor

    // FROM THE CASEFILE — BITQY

    Funds you sent to bitqy (bitqy.cc) 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 bitqy.cc:

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

    • bitqy’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 bitqy off-ramp wallet against historical laundering throughput.
    • The bitqy packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for bitqy, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

    How a bitqy casefile becomes a regulator-ready filing:

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

    What the on-chain reading covers:

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

    What the Professor will never do — by policy:

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

    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

  • Casefile Bilitex — The Professor’s Note

    // FROM THE CASEFILE — BILITEX

    Funds you sent to Bilitex (bilitex.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.

    The annotation reads — wallet trace:

    • Deposit transaction hashes from the claimant wallet to the Bilitex 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.

    From the lectern — off-ramp identification:

    • Bilitex’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 Bilitex off-ramp wallet against historical laundering throughput.
    • The Bilitex packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for Bilitex, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

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

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

    What we read in a Bilitex casefile:

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

    Recovery scammers do these things; the Professor never does:

    • Bilitex policy — seed phrases are never requested.
    • Bilitex policy — remote-access logins are never requested.
    • Bilitex policy — no upfront cash retainer to scope.
    • Bilitex policy — no guaranteed-recovery language. None.
    • Bilitex 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

  • Belet Limited — Annotated by the Professor

    // FROM THE CASEFILE — BELET LIMITED

    Belet Limited is a casefile under reading. The deposits to beletlimited.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 Belet Limited:

    • Deposit transaction hashes from the claimant wallet to the Belet Limited 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:

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

    How a Belet Limited casefile becomes a regulator-ready filing:

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

    What we read in a Belet Limited casefile:

    • Chains the Belet Limited 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 Belet Limited — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the Belet Limited 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:

    • Boundary on Belet Limited — seed phrases are off-limits.
    • Boundary on Belet Limited — remote logins are off-limits.
    • Boundary on Belet Limited — upfront cash retainers are off-limits.
    • Boundary on Belet Limited — guaranteed-recovery promises are off-limits.
    • Boundary on Belet Limited — 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

  • Casefile PRIVE FINANCE — The Professor’s Note

    // FROM THE CASEFILE — PRIVE FINANCE

    PRIVE FINANCE, operating from prive.finance, 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 — PRIVE FINANCE casefile:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for PRIVE FINANCE.
    • 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 annotation continues — off-ramp endpoint:

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

    The Professor’s recovery note for PRIVE FINANCE:

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

    What the casefile records — chains and counterparties:

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

    What the Professor will never do — by policy:

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

  • Reading the Chain: PROFITTRADE

    // FROM THE CASEFILE — PROFITTRADE

    When a deposit ledgered to PROFITTRADE at profittrade.live 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 PROFITTRADE’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 — PROFITTRADE casefile:

    • PROFITTRADE off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The PROFITTRADE 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 PROFITTRADE — the packet meets the off-ramp’s published compliance standard.
    • When the PROFITTRADE 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 triage on PROFITTRADE — the submission is read; a written assessment is delivered.
    2. Forensic trace on PROFITTRADE — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the PROFITTRADE endpoint is named.
    4. Recovery filing on PROFITTRADE — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of PROFITTRADE — the Professor follows the casefile until next-step documentation exists.

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: Spring Gold

    // FROM THE CASEFILE — SPRING GOLD

    Funds you sent to Spring Gold (springgold.net) 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.

    The annotation reads — wallet trace:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Spring Gold.
    • 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 map — where the funds left the chain:

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

    How a Spring Gold casefile becomes a regulator-ready filing:

    1. Triage on Spring Gold — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on Spring Gold — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on Spring Gold — off-ramp endpoint matched to a named exchange counterparty.
    4. File the Spring Gold 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 Spring Gold — the Professor stays on the casefile until a documented next step exists.

    Chains and off-ramps the Professor follows:

    • Deposit-side chains in Spring Gold 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 Spring Gold packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Spring Gold — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    Boundaries on every Spring Gold casefile — never crossed:

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

    // FROM THE CASEFILE — COIN HULL

    When deposits to Coin Hull via coinhull.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.

    The annotation reads — wallet trace:

    • Initial deposit hashes to the Coin Hull receiving address at coinhull.org.
    • 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 — Coin Hull casefile:

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

    Reading-list — chains and exchanges in scope:

    • Chains the Coin Hull 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 Coin Hull — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the Coin Hull 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 Coin Hull casefile — never crossed:

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

    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: CCF Markets

    // FROM THE CASEFILE — CCF MARKETS

    CCF Markets is a casefile under reading. The deposits to ccfmarkets.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:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for CCF Markets.
    • 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 map — where the funds left the chain:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the casefile records — chains and counterparties:

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

    Recovery scammers do these things; the Professor never does:

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

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

    // FROM THE CASEFILE — FOREXPRESS

    When deposits to Forexpress via forexpress.trade 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.

    The annotation reads — wallet trace:

    • Initial deposit hashes to the Forexpress receiving address at forexpress.trade.
    • 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 map — where the funds left the chain:

    • Forexpress off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Forexpress 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 Forexpress — the packet meets the off-ramp’s published compliance standard.
    • When the Forexpress 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 Forexpress:

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

    What we read in a Forexpress casefile:

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

    Recovery scammers do these things; the Professor never does:

    • Boundary on Forexpress — seed phrases are off-limits.
    • Boundary on Forexpress — remote logins are off-limits.
    • Boundary on Forexpress — upfront cash retainers are off-limits.
    • Boundary on Forexpress — guaranteed-recovery promises are off-limits.
    • Boundary on Forexpress — 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

  • GFund Assets — Annotated by the Professor

    // FROM THE CASEFILE — GFUND ASSETS

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

    The annotation reads — wallet trace:

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

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

    How a GFund Assets casefile becomes a regulator-ready filing:

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

    Chains and off-ramps the Professor follows:

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

    Lines we never cross — by published policy:

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

    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