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.

  • Office Hours on ActivFX

    // FROM THE CASEFILE — ACTIVFX

    Funds you sent to ActivFX (activ-fx.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 ActivFX 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 annotation continues — off-ramp endpoint:

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

    How a ActivFX casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    What is never asked of a claimant:

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

    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

  • Casefile UVSBIT — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

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

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

    How a UVSBIT casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    UVSBIT has been flagged as a fake broker/platform by IOSCO I-SCAN (British Columbia – British Columbia Securities Commission). reported 2026-01-23. 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/

  • DollreX Capital — Annotated by the Professor

    // FROM THE CASEFILE — DOLLREX CAPITAL

    DollreX Capital, operating from dollrexcapital.com, 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 — DollreX Capital casefile:

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

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

    The Professor’s recovery note for DollreX Capital:

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

    What we read in a DollreX Capital casefile:

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

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

    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: Silversgate Bank

    // FROM THE CASEFILE — WORLD MARKETS

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

    On-chain reading — wallet flow for Silversgate Bank:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Silversgate Bank has been flagged as a fake broker/platform by IOSCO I-SCAN (New Zealand – Financial Markets Authority). reported 2026-04-09. 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/

  • Casefile My Financial Advisor Pty Ltd — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

    The Professor opens the file on My Financial Advisor Pty Ltd 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 My Financial Advisor Pty Ltd.
    • Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
    • Cross-chain bridge events to chains with deeper exchange liquidity.
    • Privacy-service interactions, where present in the trail.
    • Off-ramp wallet — the named centralised-exchange endpoint.

    From the lectern — off-ramp identification:

    • My Financial Advisor Pty Ltd off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The My Financial Advisor Pty Ltd off-ramp address is matched to known compliance feeds — the Professor’s standing dataset plus chain-analytics references.
    • Compliance leverage is applied at the named counterparty for My Financial Advisor Pty Ltd — the packet meets the off-ramp’s published compliance standard.
    • When the My Financial Advisor Pty Ltd off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

    How a My Financial Advisor Pty Ltd casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    My Financial Advisor Pty Ltd has been flagged as a fake broker/platform by IOSCO I-SCAN (Australia – Australian Securities and Investments Commission). reported 2026-07-03. Jurisdiction: Australia. 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: UBSD FX

    // FROM THE CASEFILE — UBSD FX

    Funds you sent to UBSD FX (tdcfx.com) are still recorded on the public ledger; the question is no longer whether the money moved but where the off-ramp opened — and that is what the Professor reads.

    The annotation reads — wallet trace:

    • Deposit confirmations from the claimant to UBSD FX’s receiving wallet at tdcfx.com.
    • Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
    • Cross-chain bridge transactions where the operator routed value out of the deposit chain.
    • Mixer or coin-join interactions, where applicable.
    • Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

    The annotation continues — off-ramp endpoint:

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

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

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

    Reading-list — chains and exchanges in scope:

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

    What the Professor will never do — by policy:

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

    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 TRDFX

    // FROM THE CASEFILE — TRDFX

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

    Wallet trace — what the Professor maps:

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

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

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

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

    Chains and off-ramps the Professor follows:

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

    Boundaries on every TRDFX casefile — never crossed:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: SandStone FX

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to SandStone FX via https: 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 SandStone FX:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    SandStone FX has been flagged as a fake broker/platform by IOSCO I-SCAN (United Kingdom – Financial Conduct Authority). reported 2026-05-20. 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 Piyasa Servet — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

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

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

    How a Piyasa Servet casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    Piyasa Servet has been flagged as a fake broker/platform by IOSCO I-SCAN (United Kingdom – Financial Conduct Authority). reported 2026-05-08. 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/

  • Reading the Chain: Maunto

    // FROM THE CASEFILE — MAUNTO

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

    The annotation reads — wallet trace:

    • Initial deposit hashes to the Maunto receiving address at maunto.net.
    • 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:

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

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

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

    Chains and off-ramps the Professor follows:

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

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

    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