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

Tag: recovery company

  • Professor’s Brief: Fake DooPrime

    // FROM THE CASEFILE — FAKE DOOPRIME

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

    On-chain reading — wallet flow for Fake DooPrime:

    • Deposit confirmations from the claimant to Fake DooPrime’s receiving wallet at dooprimes.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:

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

    How a Fake DooPrime casefile becomes a regulator-ready filing:

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

    What the Professor tracks across Fake DooPrime casefiles:

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

    Lines we never cross — by published policy:

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

    Open a free consultation

    Submit your wallet for a forensic reading — /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Smartcoinfx

    // FROM THE CASEFILE — SMARTCOINFX

    Smartcoinfx is a casefile under reading. The deposits to smartcoinfx.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 smartcoinfx.com:

    • Deposit confirmations from the claimant to Smartcoinfx’s receiving wallet at smartcoinfx.com.
    • Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
    • Cross-chain bridge transactions where the operator routed value out of the deposit chain.
    • Mixer or coin-join interactions, where applicable.
    • Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

    Off-ramp summary — Smartcoinfx casefile:

    • Smartcoinfx off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Smartcoinfx 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 Smartcoinfx — the packet meets the off-ramp’s published compliance standard.
    • When the Smartcoinfx 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. Submission triage — Smartcoinfx casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — Smartcoinfx deposit and forwarding wallets captured.
    3. Endpoint identification — Smartcoinfx off-ramp wallet named.
    4. Filing — Smartcoinfx packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — Smartcoinfx stays on file until a documented next step is reached.

    What the on-chain reading covers:

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

    What the Professor will never do — by policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Fomobitmax — Annotated by the Professor

    // FROM THE CASEFILE — FOMOBITMAX

    When deposits to Fomobitmax via fomobitmax.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.

    Wallet trace — what the Professor maps:

    • Claimant-to-platform deposit transactions on the deposit chain used by Fomobitmax.
    • 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 annotation continues — off-ramp endpoint:

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

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

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

    Chains and off-ramps the Professor follows:

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

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

    // FROM THE CASEFILE — MBCHAINS

    Funds you sent to MBCHAINS (mbchains.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:

    • Deposit transaction hashes from the claimant wallet to the MBCHAINS platform receiving address.
    • Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
    • Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
    • Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
    • Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

    Off-ramp reading — exchange counterparty for MBCHAINS:

    • MBCHAINS’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 MBCHAINS off-ramp wallet against historical laundering throughput.
    • The MBCHAINS packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for MBCHAINS, 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. Casefile review on MBCHAINS — reading the submission against the no-go list.
    2. Trace mapping on MBCHAINS — pathway documented to chain-of-custody standard.
    3. Off-ramp naming on MBCHAINS — exchange endpoint identified.
    4. Packet filing on MBCHAINS — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
    5. Documented follow-through on MBCHAINS.

    What we read in a MBCHAINS casefile:

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

    Lines the Professor will not cross:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: RV Markets

    // FROM THE CASEFILE — RV MARKETS

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

    Wallet trace — what the Professor maps:

    • Deposit transaction hashes from the claimant wallet to the RV Markets platform receiving address.
    • Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
    • Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
    • Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
    • Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

    Off-ramp reading — exchange counterparty for RV Markets:

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

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

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

    What the casefile records — chains and counterparties:

    • Chains the Professor reads for RV Markets casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
    • Off-ramps named in RV Markets — major centralised venues with compliance desks that accept regulator-grade packets.
    • Filing pathways available on RV Markets — 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:

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

    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

  • GammaFx — Annotated by the Professor

    // FROM THE CASEFILE — GAMMAFX

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

    Wallet trace — what the Professor maps:

    • Deposit transaction hashes from the claimant wallet to the GammaFx 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 annotation continues — off-ramp endpoint:

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

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

    What the Professor tracks across GammaFx casefiles:

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

    Lines we never cross — by published policy:

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

  • FOREIGNMARKETOPTIONS LIMITED (FMO) — Annotated by the Professor

    // FROM THE CASEFILE — FOREIGNMARKETOPTIONS LIMITED (FMO)

    FOREIGNMARKETOPTIONS LIMITED (FMO) is a casefile under reading. The deposits to foreignmarketoptions.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.

    On-chain reading — wallet flow for FOREIGNMARKETOPTIONS LIMITED (FMO):

    • Deposit confirmations from the claimant to FOREIGNMARKETOPTIONS LIMITED (FMO)’s receiving wallet at foreignmarketoptions.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:

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

    The Professor’s recovery note for FOREIGNMARKETOPTIONS LIMITED (FMO):

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

    Reading-list — chains and exchanges in scope:

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

    Boundaries on every FOREIGNMARKETOPTIONS LIMITED (FMO) casefile — never crossed:

    • Boundary on FOREIGNMARKETOPTIONS LIMITED (FMO) — seed phrases are off-limits.
    • Boundary on FOREIGNMARKETOPTIONS LIMITED (FMO) — remote logins are off-limits.
    • Boundary on FOREIGNMARKETOPTIONS LIMITED (FMO) — upfront cash retainers are off-limits.
    • Boundary on FOREIGNMARKETOPTIONS LIMITED (FMO) — guaranteed-recovery promises are off-limits.
    • Boundary on FOREIGNMARKETOPTIONS LIMITED (FMO) — unsolicited outbound contact is off-limits.

    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

  • Capitrades — Annotated by the Professor

    // FROM THE CASEFILE — CAPITRADES

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

    The annotation reads — wallet trace:

    • Initial deposit hashes to the Capitrades receiving address at capitrades.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 reading — exchange counterparty for Capitrades:

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

    How a Capitrades casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

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

    Open a free consultation

    Submit your wallet for a forensic reading — /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: Indexx Club

    // FROM THE CASEFILE — INDEXX CLUB

    Indexx Club is a casefile under reading. The deposits to indexxclub.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:

    • Claimant-to-platform deposit transactions on the deposit chain used by Indexx Club.
    • 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 summary — Indexx Club casefile:

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

    The Professor’s recovery note for Indexx Club:

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

    What we read in a Indexx Club casefile:

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

    Lines we never cross — by published policy:

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

    Open a free consultation

    The Professor reads claims at no charge to begin — open a consultation at /contact-us/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: Quanta Capital

    // FROM THE CASEFILE — QUANTA CAPITAL

    When deposits to Quanta Capital via quantacapital.com.co 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 Quanta Capital:

    • Initial deposit hashes to the Quanta Capital receiving address at quantacapital.com.co.
    • 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 annotation continues — off-ramp endpoint:

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

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

    What the on-chain reading covers:

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

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

    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