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

Tag: recovery company

  • Fake SohoMarkets — Annotated by the Professor

    // FROM THE CASEFILE — FAKE SOHOMARKETS

    When deposits to Fake SohoMarkets via soho-markets.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.

    From the marginalia — the deposit pathway:

    • Deposit-side hashes from claimant wallets into Fake SohoMarkets’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 annotation continues — off-ramp endpoint:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What we read in a Fake SohoMarkets casefile:

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

    What the Professor will never do — by policy:

    • Recovery scammers do these things on Fake SohoMarkets; the Professor never does — request seed phrases.
    • Recovery scammers do these things on Fake SohoMarkets; the Professor never does — request remote logins.
    • Recovery scammers do these things on Fake SohoMarkets; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on Fake SohoMarkets; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on Fake SohoMarkets; 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

  • MGF Capital — Annotated by the Professor

    // FROM THE CASEFILE — MGF CAPITAL

    When deposits to MGF Capital via mgfcap.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 mgfcap.com:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the Professor tracks across MGF Capital casefiles:

    • Chains the MGF Capital 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 MGF Capital — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the MGF Capital 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 the Professor will not cross:

    • MGF Capital policy — seed phrases are never requested.
    • MGF Capital policy — remote-access logins are never requested.
    • MGF Capital policy — no upfront cash retainer to scope.
    • MGF Capital policy — no guaranteed-recovery language. None.
    • MGF Capital policy — no unsolicited calls. The Professor responds in writing 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

  • TPK Trading — Annotated by the Professor

    // FROM THE CASEFILE — TPK TRADING

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

    Trace summary — funds that left tpktrading.com:

    • Deposit confirmations from the claimant to TPK Trading’s receiving wallet at tpktrading.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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Allpips — The Professor’s Note

    // FROM THE CASEFILE — ALLPIPS

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

    On-chain reading — wallet flow for Allpips:

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

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

    How a Allpips casefile becomes a regulator-ready filing:

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

    What the on-chain reading covers:

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

    Boundaries on every Allpips casefile — never crossed:

    • Recovery scammers do these things on Allpips; the Professor never does — request seed phrases.
    • Recovery scammers do these things on Allpips; the Professor never does — request remote logins.
    • Recovery scammers do these things on Allpips; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on Allpips; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on Allpips; 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

  • Professor’s Brief: QUANTA

    // FROM THE CASEFILE — QUANTA

    The Professor opens the file on QUANTA 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 — QUANTA casefile:

    • Deposit-side hashes from claimant wallets into QUANTA’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 reading — exchange counterparty for QUANTA:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the casefile records — chains and counterparties:

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

    Lines we never cross — by published policy:

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

  • Casefile Forepay — The Professor’s Note

    // FROM THE CASEFILE — FOREPAY

    Funds you sent to Forepay (forepay.co) 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-side hashes from claimant wallets into Forepay’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 reading — exchange counterparty for Forepay:

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

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

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

    Chains and off-ramps the Professor follows:

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

  • Office Hours on PrimeWave Forex

    // FROM THE CASEFILE — PRIMEWAVE FOREX

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

    From the marginalia — the deposit pathway:

    • Deposit-side hashes from claimant wallets into PrimeWave Forex’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 annotation continues — off-ramp endpoint:

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

    How a PrimeWave Forex casefile becomes a regulator-ready filing:

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

    What the casefile records — chains and counterparties:

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

    What the Professor will never do — by policy:

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

    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

  • Octafx trade — Annotated by the Professor

    // FROM THE CASEFILE — OCTAFX TRADE

    When a deposit ledgered to Octafx trade at brokersfxt.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:

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

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

    The Professor’s recovery note for Octafx trade:

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

    What the casefile records — chains and counterparties:

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

    Lines the Professor will not cross:

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

    // FROM THE CASEFILE — EVA MARKETS

    Eva Markets, operating from evamarkets.com, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    From the marginalia — the deposit pathway:

    • Deposit-side hashes from claimant wallets into Eva Markets’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:

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

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

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

    Reading-list — chains and exchanges in scope:

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

    Lines the Professor will not cross:

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

    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: Clone IUX

    // FROM THE CASEFILE — CLONE IUX

    When deposits to Clone IUX via iuxmarketsfx.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.

    Reading the wallets — Clone IUX casefile:

    • Deposit confirmations from the claimant to Clone IUX’s receiving wallet at iuxmarketsfx.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 annotation continues — off-ramp endpoint:

    • Clone IUX off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Clone IUX 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 Clone IUX — the packet meets the off-ramp’s published compliance standard.
    • When the Clone IUX 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. Read the Clone IUX submission — written go/no-go returned.
    2. Map the Clone IUX wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the Clone IUX off-ramp — endpoint counterparty identified.
    4. Build and file the Clone IUX recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the Clone IUX file — until written next steps exist.

    What we read in a Clone IUX casefile:

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

    Recovery scammers do these things; the Professor never does:

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

    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