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

Tag: crypto scam recovery

  • Office Hours on forexeze.com

    // FROM THE CASEFILE — FOREXEZE.COM

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

    On-chain reading — wallet flow for forexeze.com:

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

    The annotation continues — off-ramp endpoint:

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

    The Professor’s recovery note for forexeze.com:

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

    What the Professor tracks across forexeze.com casefiles:

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

    What is never asked of a claimant:

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

  • Casefile National Cyber Security Centre (Imposter) — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

    The Professor opens the file on National Cyber Security Centre (Imposter) 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 National Cyber Security Centre (Imposter).
    • 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:

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

    How a National Cyber Security Centre (Imposter) casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    National Cyber Security Centre (Imposter) has been flagged as a fake broker/platform by IOSCO I-SCAN (New Zealand – Financial Markets Authority). reported 2025-11-28. 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/

  • From the Lectern: White Forex

    // FROM THE CASEFILE — WHITE FOREX

    The Professor opens the file on White Forex 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 White Forex receiving address at whiteforex.com.
    • Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
    • Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
    • Obfuscation events through mixer contracts and privacy services.
    • Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

    The Professor’s off-ramp note:

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

    The Professor’s recovery note for White Forex:

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

    Chains and off-ramps the Professor follows:

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

    Lines we never cross — by published policy:

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

    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 Expeke

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to Expeke via ;wallet.expeke.net 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 ;wallet.expeke.net:

    • Deposit confirmations from the claimant to Expeke’s receiving wallet at ;wallet.expeke.net.
    • 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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Expeke 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/

  • Reading the Chain: Cunningham, Austin, Wheeler & Associates

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Cunningham, Austin, Wheeler & Associates via cunninghamaustinwheeler.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 Cunningham, Austin, Wheeler & Associates:

    • Claimant-to-platform deposit transactions on the deposit chain used by Cunningham, Austin, Wheeler & Associates.
    • 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 Cunningham, Austin, Wheeler & Associates:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Cunningham, Austin, Wheeler & Associates 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 Ally Fortress — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

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

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

    How a Ally Fortress casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    Ally Fortress has been flagged as a fake broker/platform by IOSCO I-SCAN (British Columbia – British Columbia Securities Commission). reported 2025-07-21. 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/

  • Casefile IkasFX — The Professor’s Note

    // FROM THE CASEFILE — IKASFX

    Funds you sent to IkasFX (ikasforex.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.

    On-chain reading — wallet flow for IkasFX:

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

    • Endpoint counterparty in the IkasFX casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • IkasFX’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 IkasFX packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the IkasFX off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

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

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

    What we read in a IkasFX casefile:

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

    Boundaries on every IkasFX casefile — never crossed:

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

    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 Enerdex

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to Enerdex via enerdex.top 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 enerdex.top:

    • Deposit confirmations from the claimant to Enerdex’s receiving wallet at enerdex.top.
    • 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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

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

  • Reading the Chain: Whitehouse Capital Pte Ltd

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Whitehouse Capital 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 Whitehouse Capital Pte Ltd:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Whitehouse Capital 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: BILUXFITEX

    // FROM THE CASEFILE — BILUXFITEX

    When deposits to BILUXFITEX via biluxfitex.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.

    From the marginalia — the deposit pathway:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for BILUXFITEX.
    • 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 BILUXFITEX 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 BILUXFITEX is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the BILUXFITEX casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, BILUXFITEX escalates to IC3, state AG, and civil-discovery overlay.

    Recovery pathway — how this casefile moves toward filing:

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

    Reading-list — chains and exchanges in scope:

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

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace