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 →

Tag: recover stolen crypto

  • Office Hours on Mudresinvest FX

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

    When deposits to Mudresinvest FX via mudresinvestfx.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 Mudresinvest FX 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:

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

    How a Mudresinvest FX casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    Mudresinvest FX 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: RBI Holding Pte Ltd

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to RBI Holding Pte Ltd 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 RBI Holding Pte Ltd:

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

    Off-ramp reading — exchange counterparty for RBI Holding Pte Ltd:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    RBI Holding Pte Ltd has been flagged as a fake broker/platform by IOSCO I-SCAN (Singapore – Monetary Authority of Singapore). reported 2026-03-30. Jurisdiction: Singapore. 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: Bitcoin 365

    // FROM THE CASEFILE — BITCOIN 365

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

    On-chain reading — wallet flow for Bitcoin 365:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Bitcoin 365.
    • Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
    • Bridge events into chains where the operator can off-ramp at scale.
    • Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
    • Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

    Off-ramp map — where the funds left the chain:

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

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

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

    What we read in a Bitcoin 365 casefile:

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

    What the Professor will never do — by policy:

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

  • Office Hours on MHT Holdings

    // FROM THE CASEFILE — MHT HOLDINGS

    MHT Holdings, operating from mhtholdings.org, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    From the marginalia — the deposit pathway:

    • Deposit transaction hashes from the claimant wallet to the MHT Holdings 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 summary — MHT Holdings casefile:

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

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

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

    What the casefile records — chains and counterparties:

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

    Lines we never cross — by published policy:

    • On the MHT Holdings casefile — never request a seed phrase. Ever.
    • On the MHT Holdings casefile — never request remote-access logins to a wallet or exchange.
    • On the MHT Holdings casefile — never demand an upfront cash retainer to scope the matter.
    • On the MHT Holdings casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the MHT Holdings casefile — never call the claimant unsolicited. Written-only.

    Open a free consultation

    Send the wallet for trace — /submit-a-case/ — the Professor responds in writing.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Quantfury

    // FROM THE CASEFILE — CTK NETWORK

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

    Trace summary — funds that left quantfury.com:

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

    From the lectern — off-ramp identification:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Quantfury has been flagged as a fake broker/platform by IOSCO I-SCAN (France – Autorité des marchés financiers). reported 2026-02-06. Jurisdiction: France. 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 TRANZI

    // FROM THE CASEFILE — TRANZI

    Funds you sent to TRANZI (tranziinternational.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.

    Trace summary — funds that left tranziinternational.com:

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

    Off-ramp reading — exchange counterparty for TRANZI:

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

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

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

    What we read in a TRANZI casefile:

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

    Boundaries on every TRANZI casefile — never crossed:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: Fx Edge Prime Pro

    // FROM THE CASEFILE — FX EDGE PRIME PRO

    When a deposit ledgered to Fx Edge Prime Pro at fxedgeprimepro.com stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    Reading the wallets — Fx Edge Prime Pro casefile:

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

    From the lectern — off-ramp identification:

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

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

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

    What we read in a Fx Edge Prime Pro casefile:

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

    What the Professor will never do — by policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: Subscribe To investment units

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Subscribe To investment units 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 Subscribe To investment units:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Subscribe To investment units has been flagged as a fake broker/platform by IOSCO I-SCAN (Thailand – Securities and Exchange Commission). reported 2026-03-17. Jurisdiction: Thailand. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.iosco.org/i-scan/

  • From the Lectern: Arobridge

    // FROM THE CASEFILE — AROBRIDGE

    Funds you sent to Arobridge (arobridge.co.uk) 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.

    From the marginalia — the deposit pathway:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    What is never asked of a claimant:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Saxo Stock — Annotated by the Professor

    // FROM THE CASEFILE — SAXO STOCK

    Saxo Stock, operating from saxo-stock.com, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    The annotation reads — wallet trace:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Saxo Stock.
    • Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
    • Bridge events into chains where the operator can off-ramp at scale.
    • Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
    • Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

    Off-ramp map — where the funds left the chain:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Lines the Professor will not cross:

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