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

Tag: report a scam

  • Casefile COMEX GROUP — The Professor’s Note

    // FROM THE CASEFILE — COMEX GROUP

    When deposits to COMEX GROUP via ccfgroupam.com;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.

    Wallet trace — what the Professor maps:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    What is never asked of a claimant:

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

    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

  • Reading the Chain: WealthWeaver

    // FROM THE CASEFILE — WORLD MARKETS

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

    On-chain reading — wallet flow for WealthWeaver:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    WealthWeaver has been flagged as a fake broker/platform by IOSCO I-SCAN (British Columbia – British Columbia Securities Commission). reported 2026-06-05. 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 Keystone Corporate Group — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

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

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

    How a Keystone Corporate Group casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    Keystone Corporate Group 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/

  • From the Lectern: HFX SwiftCapita

    // FROM THE CASEFILE — HFX SWIFTCAPITA

    When a deposit ledgered to HFX SwiftCapita at hfx-swiftcapita.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 confirmations from the claimant to HFX SwiftCapita’s receiving wallet at hfx-swiftcapita.com.
    • Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
    • Cross-chain bridge transactions where the operator routed value out of the deposit chain.
    • Mixer or coin-join interactions, where applicable.
    • Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

    The Professor’s off-ramp note:

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

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

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

    Chains and off-ramps the Professor follows:

    • Chains the HFX SwiftCapita 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 HFX SwiftCapita — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the HFX SwiftCapita 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 HFX SwiftCapita — seed phrases are off-limits.
    • Boundary on HFX SwiftCapita — remote logins are off-limits.
    • Boundary on HFX SwiftCapita — upfront cash retainers are off-limits.
    • Boundary on HFX SwiftCapita — guaranteed-recovery promises are off-limits.
    • Boundary on HFX SwiftCapita — unsolicited outbound contact is off-limits.

    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: DIGITAL FIRST MARKETS

    // FROM THE CASEFILE — DIGITAL FIRST MARKETS

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

    On-chain reading — wallet flow for DIGITAL FIRST MARKETS:

    • Initial deposit hashes to the DIGITAL FIRST MARKETS receiving address at digitalfirstmarkets.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.

    Off-ramp summary — DIGITAL FIRST MARKETS casefile:

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

    The Professor’s recovery note for DIGITAL FIRST MARKETS:

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

    What the casefile records — chains and counterparties:

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

    Lines we never cross — by published policy:

    • DIGITAL FIRST MARKETS policy — seed phrases are never requested.
    • DIGITAL FIRST MARKETS policy — remote-access logins are never requested.
    • DIGITAL FIRST MARKETS policy — no upfront cash retainer to scope.
    • DIGITAL FIRST MARKETS policy — no guaranteed-recovery language. None.
    • DIGITAL FIRST MARKETS policy — no unsolicited calls. The Professor responds in writing 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: Prosperity Peak Trading LLC

    // FROM THE CASEFILE — PROSPERITY PEAK TRADING LLC

    Prosperity Peak Trading LLC is a casefile under reading. The deposits to prospeaktradingllc.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.

    From the marginalia — the deposit pathway:

    • Deposit-side hashes from claimant wallets into Prosperity Peak Trading LLC’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.

    Off-ramp summary — Prosperity Peak Trading LLC casefile:

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

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

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

    Chains and off-ramps the Professor follows:

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

    What is never asked of a claimant:

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

    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 SwissTrade.pro

    // FROM THE CASEFILE — SWISSTRADE.PRO

    Funds you sent to SwissTrade.pro (swisstrade.pro) 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:

    • Claimant-to-platform deposit transactions on the deposit chain used by SwissTrade.pro.
    • Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
    • Cross-chain bridge events to chains with deeper exchange liquidity.
    • Privacy-service interactions, where present in the trail.
    • Off-ramp wallet — the named centralised-exchange endpoint.

    From the lectern — off-ramp identification:

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

    How a SwissTrade.pro casefile becomes a regulator-ready filing:

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

    Chains and off-ramps the Professor follows:

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

    What is never asked of a claimant:

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

    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

  • Reading the Chain: xcgin

    // FROM THE CASEFILE — XCGIN

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

    The annotation reads — wallet trace:

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

    The Professor’s off-ramp note:

    • Off-ramp endpoint for xcgin resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • xcgin’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for xcgin is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the xcgin 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. First read on xcgin — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on xcgin — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for xcgin is named to a centralised exchange wallet.
    4. Packet filing on xcgin — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with xcgin until a documented outcome or escalation step is on file.

    What the casefile records — chains and counterparties:

    • Chains the xcgin 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 xcgin — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the xcgin 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 the Professor will never do — by policy:

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

    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 Element Trade MT5

    // FROM THE CASEFILE — ELEMENT TRADE MT5

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

    Trace summary — funds that left elementrader.com:

    • Initial deposit hashes to the Element Trade MT5 receiving address at elementrader.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:

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

    The Professor’s recovery note for Element Trade MT5:

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

    What the casefile records — chains and counterparties:

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

    What the Professor will never do — by policy:

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

    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

  • Reading the Chain: IM Market

    // FROM THE CASEFILE — IM MARKET

    The Professor opens the file on IM Market 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 deposit hashes — provided in the case submission and verified against the public ledger for IM Market.
    • 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 summary — IM Market casefile:

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

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

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

    What the casefile records — chains and counterparties:

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

    What is never asked of a claimant:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace