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

Category: Scam Brokers

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

  • Reading the Chain: Market4Trade

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Market4Trade 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.

    On-chain reading — wallet flow for Market4Trade:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

    • Chains tracked on Market4Trade — 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 Market4Trade — named exchange counterparties with public compliance contacts.
    • Filings supported on Market4Trade — 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:

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

    Why this platform is on our casefile

    Market4Trade has been flagged as a Fraudulent online trading platforms by FSMA Belgium. FSMA warning 29/08/2024. Jurisdiction: BE. 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.fsma.be/en/warnings/companies-operating-unlawfully-in-belgium

  • Professor’s Brief: balitrade.online

    // FROM THE CASEFILE — BALITRADE.ONLINE

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

    Reading the wallets — balitrade.online casefile:

    • Initial deposit hashes to the balitrade.online receiving address at balitrade.online.
    • 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:

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

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

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

    What we read in a balitrade.online casefile:

    • Chains tracked on balitrade.online — 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 balitrade.online — named exchange counterparties with public compliance contacts.
    • Filings supported on balitrade.online — 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 balitrade.online casefile — never request a seed phrase. Ever.
    • On the balitrade.online casefile — never request remote-access logins to a wallet or exchange.
    • On the balitrade.online casefile — never demand an upfront cash retainer to scope the matter.
    • On the balitrade.online casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the balitrade.online 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

  • Casefile Royal Offshore Trust — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

    The Professor opens the file on Royal Offshore Trust 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 Royal Offshore Trust.
    • 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:

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

    How a Royal Offshore Trust casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

    • Deposit-side chains in Royal Offshore Trust 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 Royal Offshore Trust packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Royal Offshore Trust — 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 Royal Offshore Trust casefile — never request a seed phrase. Ever.
    • On the Royal Offshore Trust casefile — never request remote-access logins to a wallet or exchange.
    • On the Royal Offshore Trust casefile — never demand an upfront cash retainer to scope the matter.
    • On the Royal Offshore Trust casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the Royal Offshore Trust 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

    Royal Offshore Trust has been flagged as a fake broker/platform by IOSCO I-SCAN (New Zealand – Financial Markets Authority). reported 2026-03-03. Jurisdiction: New Zealand. 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/

  • Reading the Chain: Bitfxmarket

    // FROM THE CASEFILE — BITFXMARKET

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

    Trace summary — funds that left bitfxmarket.com:

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

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

    How a Bitfxmarket casefile becomes a regulator-ready filing:

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

    What the casefile records — chains and counterparties:

    • Deposit-side chains in Bitfxmarket 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 Bitfxmarket packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Bitfxmarket — 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 Bitfxmarket casefile — never request a seed phrase. Ever.
    • On the Bitfxmarket casefile — never request remote-access logins to a wallet or exchange.
    • On the Bitfxmarket casefile — never demand an upfront cash retainer to scope the matter.
    • On the Bitfxmarket casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the Bitfxmarket casefile — never call the claimant unsolicited. Written-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

  • Reading the Chain: 8xtrade

    // FROM THE CASEFILE — 8XTRADE

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

    Trace summary — funds that left 8xtrade.com:

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

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

    The Professor’s recovery note for 8xtrade:

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

    What the on-chain reading covers:

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

    Lines the Professor will not cross:

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

  • OFinancial Markets — Annotated by the Professor

    // FROM THE CASEFILE — OFINANCIAL MARKETS

    OFinancial Markets, operating from ofinancial.markets, 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 — OFinancial Markets casefile:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for OFinancial 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 reading — exchange counterparty for OFinancial Markets:

    • Endpoint counterparty in the OFinancial Markets casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • OFinancial Markets’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 OFinancial Markets packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the OFinancial Markets 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.

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

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

    What the on-chain reading covers:

    • Chains tracked on OFinancial 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 OFinancial Markets — named exchange counterparties with public compliance contacts.
    • Filings supported on OFinancial Markets — 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:

    • Boundary on OFinancial Markets — seed phrases are off-limits.
    • Boundary on OFinancial Markets — remote logins are off-limits.
    • Boundary on OFinancial Markets — upfront cash retainers are off-limits.
    • Boundary on OFinancial Markets — guaranteed-recovery promises are off-limits.
    • Boundary on OFinancial Markets — 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 Bitnomics — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

    The Professor opens the file on Bitnomics 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 Bitnomics.
    • 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:

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

    How a Bitnomics casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

    • Deposit-side chains in Bitnomics 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 Bitnomics packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Bitnomics — 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 Bitnomics casefile — never request a seed phrase. Ever.
    • On the Bitnomics casefile — never request remote-access logins to a wallet or exchange.
    • On the Bitnomics casefile — never demand an upfront cash retainer to scope the matter.
    • On the Bitnomics casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the Bitnomics 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

    Bitnomics has been flagged as a Fraudulent online trading platforms by FSMA Belgium. FSMA warning 16/05/2024. Jurisdiction: BE. 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.fsma.be/en/warnings/companies-operating-unlawfully-in-belgium

  • Reading the Chain: Reclaw International Inc.

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Reclaw International Inc. via reclaws.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.

    On-chain reading — wallet flow for Reclaw International Inc.:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

    • Chains tracked on Reclaw International Inc. — 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 Reclaw International Inc. — named exchange counterparties with public compliance contacts.
    • Filings supported on Reclaw International Inc. — 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:

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

    Why this platform is on our casefile

    Reclaw International Inc. has been flagged as a fake broker/platform by IOSCO I-SCAN (United States of America – Securities and Exchange Commission). reported 2026-06-04. Jurisdiction: United States of America. 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/

  • Office Hours on Broker GMBH

    // FROM THE CASEFILE — BROKER GMBH

    When a deposit ledgered to Broker GMBH at broker.gmbh stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    The annotation reads — wallet trace:

    • Deposit confirmations from the claimant to Broker GMBH’s receiving wallet at broker.gmbh.
    • 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 map — where the funds left the chain:

    • Endpoint counterparty in the Broker GMBH casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Broker GMBH’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 Broker GMBH packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Broker GMBH 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.

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

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

    What the on-chain reading covers:

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

    What the Professor will never do — by policy:

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

  • Onotex — Annotated by the Professor

    // FROM THE CASEFILE — ONOTEX

    Onotex is a casefile under reading. The deposits to onotextrade.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.

    Wallet trace — what the Professor maps:

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

    From the lectern — off-ramp identification:

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

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

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

    Chains and off-ramps the Professor follows:

    • Chains the Professor reads for Onotex casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
    • Off-ramps named in Onotex — major centralised venues with compliance desks that accept regulator-grade packets.
    • Filing pathways available on Onotex — 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:

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

    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