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

Tag: recover lost crypto

  • Reading the Chain: Aztec Group

    // FROM THE CASEFILE — AZTEC GROUP

    Funds you sent to Aztec Group (aztecgroup.cfd) 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.

    Reading the wallets — Aztec Group casefile:

    • Deposit confirmations from the claimant to Aztec Group’s receiving wallet at aztecgroup.cfd.
    • 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:

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

    The Professor’s recovery note for Aztec Group:

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

    Chains and off-ramps the Professor follows:

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

    What the Professor will never do — by policy:

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

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to Greenbridge International via greenbridgeinternational.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 greenbridgeinternational.com:

    • Deposit confirmations from the claimant to Greenbridge International’s receiving wallet at greenbridgeinternational.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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Greenbridge International 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: SecretEA

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to SecretEA via topsecretsea.github.io 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 SecretEA:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

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

  • Office Hours on Bityard

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

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

    Wallet trace — what the Professor maps:

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

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

    How a Bityard casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

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

  • Office Hours on Eva Trades

    // FROM THE CASEFILE — EVA TRADES

    Eva Trades is a casefile under reading. The deposits to evatrades.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 evatrades.com:

    • Deposit-side hashes from claimant wallets into Eva Trades’s receiving addresses.
    • Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
    • Inter-chain bridge transactions when value moves toward off-ramp liquidity.
    • Mixer/obfuscation events the operator routed through, where present.
    • Final off-ramp endpoint and named counterparty exchange.

    The Professor’s off-ramp note:

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

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

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

    What the on-chain reading covers:

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

    Boundaries on every Eva Trades casefile — never crossed:

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

    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

  • Professor’s Brief: OXShare

    // FROM THE CASEFILE — OXSHARE

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

    Reading the wallets — OXShare casefile:

    • Deposit-side hashes from claimant wallets into OXShare’s receiving addresses.
    • Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
    • Inter-chain bridge transactions when value moves toward off-ramp liquidity.
    • Mixer/obfuscation events the operator routed through, where present.
    • Final off-ramp endpoint and named counterparty exchange.

    The Professor’s off-ramp note:

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

    Recovery pathway — how this casefile moves toward filing:

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

    Reading-list — chains and exchanges in scope:

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

    Lines the Professor will not cross:

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

  • TWMarkets — Annotated by the Professor

    // FROM THE CASEFILE — TWMARKETS

    When a deposit ledgered to TWMarkets at twmarkets.net 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 TWMarkets:

    • Deposit-side hashes from claimant wallets into TWMarkets’s receiving addresses.
    • Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
    • Inter-chain bridge transactions when value moves toward off-ramp liquidity.
    • Mixer/obfuscation events the operator routed through, where present.
    • Final off-ramp endpoint and named counterparty exchange.

    The Professor’s off-ramp note:

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

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

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

    Chains and off-ramps the Professor follows:

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

    Boundaries on every TWMarkets casefile — never crossed:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on GraysFS (clone of FCA registered firm)

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

    When deposits to GraysFS (clone of FCA registered firm) 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.

    Wallet trace — what the Professor maps:

    • Deposit transaction hashes from the claimant wallet to the GraysFS (clone of FCA registered firm) 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:

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

    How a GraysFS (clone of FCA registered firm) casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    GraysFS (clone of FCA registered firm) has been flagged as a fake broker/platform by IOSCO I-SCAN (United Kingdom – Financial Conduct Authority). reported 2026-01-16. 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: ICG Limited

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to ICG Limited via intelligencechipgrouplimited.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 ICG Limited:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    ICG Limited has been flagged as a fake broker/platform by IOSCO I-SCAN (New Zealand – Financial Markets Authority). reported 2025-12-02. 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: Placementstrategique

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Placementstrategique via placementstrategique.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 Placementstrategique:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Placementstrategique has been flagged as a fake broker/platform by IOSCO I-SCAN (France – Autorité des marchés financiers). reported 2025-10-30. 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/