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

Tag: real recovery help

  • Office Hours on NeoSwissTrade

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

    When deposits to NeoSwissTrade via neoswiss-trade.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 transaction hashes from the claimant wallet to the NeoSwissTrade 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:

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

    How a NeoSwissTrade casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

    • Chains in scope for NeoSwissTrade — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
    • Off-ramps in scope for NeoSwissTrade — named centralised exchanges with compliance leverage.
    • Filings supported on NeoSwissTrade — 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 NeoSwissTrade — ask for a seed phrase.
    • What the Professor will not do on NeoSwissTrade — request remote-access logins.
    • What the Professor will not do on NeoSwissTrade — demand cash up front.
    • What the Professor will not do on NeoSwissTrade — promise a guarantee.
    • What the Professor will not do on NeoSwissTrade — 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

    NeoSwissTrade has been flagged as a fake broker/platform by IOSCO I-SCAN (Switzerland – Swiss Financial Market Supervisory Authority). reported 2026-06-30. Jurisdiction: Switzerland. 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: Financial Trading LLC

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Financial Trading LLC via l-tradingllc.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 Financial Trading LLC:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Financial Trading LLC 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/

  • Casefile Primus Forex — The Professor’s Note

    // FROM THE CASEFILE — PRIMUS FOREX

    When a deposit ledgered to Primus Forex at primusforex.net stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    Trace summary — funds that left primusforex.net:

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

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

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

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

    Reading-list — chains and exchanges in scope:

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

    Boundaries on every Primus Forex casefile — never crossed:

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

  • Havenhold (aka Havenhold GmbH) — Annotated by the Professor

    // FROM THE CASEFILE — HAVENHOLD (AKA HAVENHOLD GMBH)

    The Professor opens the file on Havenhold (aka Havenhold GmbH) 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 havenhold.de:

    • Initial deposit hashes to the Havenhold (aka Havenhold GmbH) receiving address at havenhold.de.
    • 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.

    The annotation continues — off-ramp endpoint:

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

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

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

    What the casefile records — chains and counterparties:

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

    What the Professor will never do — by policy:

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

  • Office Hours on FlandrexBit

    // FROM THE CASEFILE — CTK NETWORK

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

    Trace summary — funds that left this platform:

    • Deposit confirmations from the claimant to FlandrexBit’s receiving wallet at this platform.
    • 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.

    From the lectern — off-ramp identification:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Why this platform is on our casefile

    FlandrexBit has been flagged as a Fraudulent online trading platforms by FSMA Belgium. FSMA warning 12/03/2026. 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: Immediate Bitwave

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Immediate Bitwave 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 Immediate Bitwave:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Immediate Bitwave has been flagged as a Fraudulent online trading platforms by FSMA Belgium. FSMA warning 14/03/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

  • From the Lectern: Clone BCP FS

    // FROM THE CASEFILE — CLONE BCP FS

    Funds you sent to Clone BCP FS (bcp-fs.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.

    Wallet trace — what the Professor maps:

    • Deposit transaction hashes from the claimant wallet to the Clone BCP FS 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 Clone BCP FS:

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

    Recovery pathway — how this casefile moves toward filing:

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

    Reading-list — chains and exchanges in scope:

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

    Recovery scammers do these things; the Professor never does:

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

  • JAFX — Annotated by the Professor

    // FROM THE CASEFILE — JAFX

    When deposits to JAFX via jafx.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.

    The annotation reads — wallet trace:

    • Deposit-side hashes from claimant wallets into JAFX’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 map — where the funds left the chain:

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

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

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

    What the casefile records — chains and counterparties:

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

    • Recovery scammers do these things on JAFX; the Professor never does — request seed phrases.
    • Recovery scammers do these things on JAFX; the Professor never does — request remote logins.
    • Recovery scammers do these things on JAFX; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on JAFX; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on JAFX; 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 FX Trade Pro Broker — The Professor’s Note

    // FROM THE CASEFILE — FX TRADE PRO BROKER

    FX Trade Pro Broker is a casefile under reading. The deposits to fxtrade.app 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-to-platform deposit transactions on the deposit chain used by FX Trade Pro Broker.
    • 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 FX Trade Pro Broker:

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

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

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

    Chains and off-ramps the Professor follows:

    • Chains the FX Trade Pro Broker casefile may touch — Bitcoin and Ethereum at the deposit side, Tron USDT-TRC20 in stablecoin pathways, BNB Smart Chain and the L2s (Arbitrum, Optimism, Polygon, Base) where bridges link them.
    • Off-ramps relevant to FX Trade Pro Broker — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the FX Trade Pro Broker 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 FX Trade Pro Broker casefile — never crossed:

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

  • Casefile NIO Capital — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

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

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

    How a NIO Capital casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    NIO Capital has been flagged as a fake broker/platform by IOSCO I-SCAN (British Columbia – British Columbia Securities Commission). reported 2026-06-26. Jurisdiction: British Columbia. 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/