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

Tag: crypto recovery

  • Office Hours on Cafe Amazon

    // FROM THE CASEFILE — CTK NETWORK

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

    Trace summary — funds that left https::

    • Deposit confirmations from the claimant to Cafe Amazon’s receiving wallet at https:.
    • 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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Cafe Amazon has been flagged as a fake broker/platform by IOSCO I-SCAN (Thailand – Securities and Exchange Commission). reported 2025-12-09. 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/

  • QuantomFX — Annotated by the Professor

    // FROM THE CASEFILE — QUANTOMFX

    QuantomFX is a casefile under reading. The deposits to quantomfx.com sit on-chain, immutable; the wallet pathway is the primary source, and the off-ramp endpoint is the conclusion the Professor’s marginalia points toward.

    Trace summary — funds that left quantomfx.com:

    • Deposit confirmations from the claimant to QuantomFX’s receiving wallet at quantomfx.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 summary — QuantomFX casefile:

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

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

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

    What we read in a QuantomFX casefile:

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

    Lines we never cross — by published policy:

    • Hard line on QuantomFX — no seed-phrase requests, period.
    • Hard line on QuantomFX — no remote logins requested.
    • Hard line on QuantomFX — no upfront cash retainer.
    • Hard line on QuantomFX — no guarantee language.
    • Hard line on QuantomFX — 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

  • Office Hours on AssetImperial

    // FROM THE CASEFILE — ASSETIMPERIAL

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

    From the marginalia — the deposit pathway:

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

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

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

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

    What the Professor tracks across AssetImperial casefiles:

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

    Recovery scammers do these things; the Professor never does:

    • Hard line on AssetImperial — no seed-phrase requests, period.
    • Hard line on AssetImperial — no remote logins requested.
    • Hard line on AssetImperial — no upfront cash retainer.
    • Hard line on AssetImperial — no guarantee language.
    • Hard line on AssetImperial — 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

  • Professor’s Brief: AstroFXbtcm

    // FROM THE CASEFILE — ASTROFXBTCM

    Funds you sent to AstroFXbtcm (astrofxbtcm.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 confirmations from the claimant to AstroFXbtcm’s receiving wallet at astrofxbtcm.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 AstroFXbtcm:

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

    The Professor’s recovery note for AstroFXbtcm:

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

    What we read in a AstroFXbtcm casefile:

    • Chains the AstroFXbtcm 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 AstroFXbtcm — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the AstroFXbtcm packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

    What is never asked of a claimant:

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

    Open a free consultation

    Bring the casefile to office hours — open a free consultation at /contact-us/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Bridgecapitalslp — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

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

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

    How a Bridgecapitalslp casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    Bridgecapitalslp has been flagged as a fake broker/platform by IOSCO I-SCAN (United Kingdom – Financial Conduct Authority). reported 2023-10-12. 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: Onemillion

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Onemillion via onemillion.team 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 Onemillion:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Onemillion has been flagged as a fake broker/platform by IOSCO I-SCAN (Spain – Comisión Nacional del Mercado de Valores). reported 2026-01-06. Jurisdiction: Spain. 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: Holding Heritage

    // FROM THE CASEFILE — HOLDING HERITAGE

    The Professor opens the file on Holding Heritage 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 Holding Heritage:

    • Deposit transaction hashes from the claimant wallet to the Holding Heritage 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 map — where the funds left the chain:

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

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

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

    What we read in a Holding Heritage casefile:

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

    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: Alphatrustcapital (Imposter)

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Alphatrustcapital (Imposter) via alphatrustcapital.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 Alphatrustcapital (Imposter):

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

    Off-ramp reading — exchange counterparty for Alphatrustcapital (Imposter):

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

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

  • Office Hours on Projectguardian.digital

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to Projectguardian.digital via stellar.expert 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 stellar.expert:

    • Deposit confirmations from the claimant to Projectguardian.digital’s receiving wallet at stellar.expert.
    • 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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Projectguardian.digital 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/

  • Casefile EFB LOANS — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

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

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

    How a EFB LOANS casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    EFB LOANS has been flagged as a fake broker/platform by IOSCO I-SCAN (United Kingdom – Financial Conduct Authority). reported 2023-12-04. 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/