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

Tag: scam broker

  • Office Hours on G7 Brics

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

    When deposits to G7 Brics via g7-brics.site 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 transaction hashes from the claimant wallet to the G7 Brics 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:

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

    How a G7 Brics casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    What the Professor will never do — by policy:

    • What the Professor will not do on G7 Brics — ask for a seed phrase.
    • What the Professor will not do on G7 Brics — request remote-access logins.
    • What the Professor will not do on G7 Brics — demand cash up front.
    • What the Professor will not do on G7 Brics — promise a guarantee.
    • What the Professor will not do on G7 Brics — 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

    Why this platform is on our casefile

    G7 Brics has been flagged as a fake broker/platform by IOSCO I-SCAN (United Kingdom – Financial Conduct Authority). reported 2025-07-10. Jurisdiction: United Kingdom. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.iosco.org/i-scan/

  • Casefile LumineTrade — The Professor’s Note

    // FROM THE CASEFILE — LUMINETRADE

    When deposits to LumineTrade via lumine-trd.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 lumine-trd.com:

    • Deposit-side hashes from claimant wallets into LumineTrade’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.

    From the lectern — off-ramp identification:

    • LumineTrade’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 LumineTrade off-ramp wallet against historical laundering throughput.
    • The LumineTrade packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for LumineTrade, 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 LumineTrade — the submission is read; a written assessment is delivered.
    2. Forensic trace on LumineTrade — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the LumineTrade endpoint is named.
    4. Recovery filing on LumineTrade — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of LumineTrade — the Professor follows the casefile until next-step documentation exists.

    Chains and off-ramps the Professor follows:

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

    What the Professor will never do — by policy:

    • Recovery scammers do these things on LumineTrade; the Professor never does — request seed phrases.
    • Recovery scammers do these things on LumineTrade; the Professor never does — request remote logins.
    • Recovery scammers do these things on LumineTrade; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on LumineTrade; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on LumineTrade; 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

  • Casefile Nex Bridge FX — The Professor’s Note

    // FROM THE CASEFILE — NEX BRIDGE FX

    Nex Bridge FX is a casefile under reading. The deposits to nexbridgefx.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 Nex Bridge FX:

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

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

    How a Nex Bridge FX casefile becomes a regulator-ready filing:

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

    What we read in a Nex Bridge FX casefile:

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

    Lines the Professor will not cross:

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

  • From the Lectern: Boney Market

    // FROM THE CASEFILE — BONEY MARKET

    When deposits to Boney Market via boneymarket.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-side hashes from claimant wallets into Boney Market’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 Professor’s off-ramp note:

    • Boney Market off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Boney Market 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 Boney Market — the packet meets the off-ramp’s published compliance standard.
    • When the Boney Market 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. Submission triage — Boney Market casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — Boney Market deposit and forwarding wallets captured.
    3. Endpoint identification — Boney Market off-ramp wallet named.
    4. Filing — Boney Market packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — Boney Market stays on file until a documented next step is reached.

    What the Professor tracks across Boney Market casefiles:

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

    Lines the Professor will not cross:

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

    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 OTC Markets

    // FROM THE CASEFILE — OTC MARKETS

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

    From the marginalia — the deposit pathway:

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

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

    How a OTC Markets casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    Lines the Professor will not cross:

    • On the OTC Markets casefile — never request a seed phrase. Ever.
    • On the OTC Markets casefile — never request remote-access logins to a wallet or exchange.
    • On the OTC Markets casefile — never demand an upfront cash retainer to scope the matter.
    • On the OTC Markets casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the OTC Markets casefile — never call the claimant unsolicited. Written-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: RXK Capital

    // FROM THE CASEFILE — RXK CAPITAL

    When a deposit ledgered to RXK Capital at rxkcapital.com stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    Reading the wallets — RXK Capital casefile:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the casefile records — chains and counterparties:

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

    What the Professor will never do — by policy:

    • What the Professor will not do on RXK Capital — ask for a seed phrase.
    • What the Professor will not do on RXK Capital — request remote-access logins.
    • What the Professor will not do on RXK Capital — demand cash up front.
    • What the Professor will not do on RXK Capital — promise a guarantee.
    • What the Professor will not do on RXK 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

  • Casefile oberonsys.com (Clone of FCA firms) — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

    The Professor opens the file on oberonsys.com (Clone of FCA firms) 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.

    From the marginalia — the deposit pathway:

    • Claimant-to-platform deposit transactions on the deposit chain used by oberonsys.com (Clone of FCA firms).
    • 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.

    From the lectern — off-ramp identification:

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

    How a oberonsys.com (Clone of FCA firms) casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    What is never asked of a claimant:

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

    Why this platform is on our casefile

    oberonsys.com (Clone of FCA firms) has been flagged as a fake broker/platform by IOSCO I-SCAN (United Kingdom – Financial Conduct Authority). reported 2026-04-09. Jurisdiction: United Kingdom. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.iosco.org/i-scan/

  • From the Lectern: ProDivia Group

    // FROM THE CASEFILE — PRODIVIA GROUP

    When a deposit ledgered to ProDivia Group at prodivia-group.com stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    Reading the wallets — ProDivia Group casefile:

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

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

    How a ProDivia Group casefile becomes a regulator-ready filing:

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

    What we read in a ProDivia Group casefile:

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

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

  • Office Hours on Gerco Capitals (uses the name of the company regulated by the FCA)

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

    When deposits to Gerco Capitals (uses the name of the company regulated by the FCA) via this platform 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 transaction hashes from the claimant wallet to the Gerco Capitals (uses the name of the company regulated by the FCA) 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:

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

    How a Gerco Capitals (uses the name of the company regulated by the FCA) casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    What the Professor will never do — by policy:

    • What the Professor will not do on Gerco Capitals (uses the name of the company regulated by the FCA) — ask for a seed phrase.
    • What the Professor will not do on Gerco Capitals (uses the name of the company regulated by the FCA) — request remote-access logins.
    • What the Professor will not do on Gerco Capitals (uses the name of the company regulated by the FCA) — demand cash up front.
    • What the Professor will not do on Gerco Capitals (uses the name of the company regulated by the FCA) — promise a guarantee.
    • What the Professor will not do on Gerco Capitals (uses the name of the company regulated by the FCA) — 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

    Why this platform is on our casefile

    Gerco Capitals (uses the name of the company regulated by the FCA) has been flagged as a fake broker/platform by IOSCO I-SCAN (Ukraine – National Securities and Stock Market Commission). reported 2024-03-22. Jurisdiction: Ukraine. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.iosco.org/i-scan/

  • Professor’s Brief: Genesis Capital

    // FROM THE CASEFILE — GENESIS CAPITAL

    When deposits to Genesis Capital via genesis-capitals.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 genesis-capitals.com:

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

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

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

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

    What the casefile records — chains and counterparties:

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

    What the Professor will never do — by policy:

    • What the Professor will not do on Genesis Capital — ask for a seed phrase.
    • What the Professor will not do on Genesis Capital — request remote-access logins.
    • What the Professor will not do on Genesis Capital — demand cash up front.
    • What the Professor will not do on Genesis Capital — promise a guarantee.
    • What the Professor will not do on Genesis Capital — 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