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

  • Ico Assets — Annotated by the Professor

    // FROM THE CASEFILE — ICO ASSETS

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

    Wallet trace — what the Professor maps:

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

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

    How a Ico Assets casefile becomes a regulator-ready filing:

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

    What the Professor tracks across Ico Assets casefiles:

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

    • What the Professor will not do on Ico Assets — ask for a seed phrase.
    • What the Professor will not do on Ico Assets — request remote-access logins.
    • What the Professor will not do on Ico Assets — demand cash up front.
    • What the Professor will not do on Ico Assets — promise a guarantee.
    • What the Professor will not do on Ico Assets — 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

  • Office Hours on A1FX

    // FROM THE CASEFILE — A1FX

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

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

    The Professor’s off-ramp note:

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

    The Professor’s recovery note for A1FX:

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

    What the on-chain reading covers:

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

    What the Professor will never do — by policy:

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

  • Casefile Forex Trading World Limited — The Professor’s Note

    // FROM THE CASEFILE — FOREX TRADING WORLD LIMITED

    Forex Trading World Limited, operating from forextradingworld.ltd, 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 forextradingworld.ltd:

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

    Off-ramp reading — exchange counterparty for Forex Trading World Limited:

    • Off-ramp endpoint for Forex Trading World Limited resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Forex Trading World Limited’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Forex Trading World Limited is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Forex Trading World Limited 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 triage on Forex Trading World Limited — the submission is read; a written assessment is delivered.
    2. Forensic trace on Forex Trading World Limited — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the Forex Trading World Limited endpoint is named.
    4. Recovery filing on Forex Trading World Limited — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of Forex Trading World Limited — the Professor follows the casefile until next-step documentation exists.

    What the on-chain reading covers:

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

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

  • From the Lectern: Axiora Trades

    // FROM THE CASEFILE — AXIORA TRADES

    Funds you sent to Axiora Trades (axioratrades.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.

    Trace summary — funds that left axioratrades.com:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Axiora Trades.
    • 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 Professor’s off-ramp note:

    • Axiora Trades off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Axiora Trades 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 Axiora Trades — the packet meets the off-ramp’s published compliance standard.
    • When the Axiora Trades 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 Axiora Trades:

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

    Reading-list — chains and exchanges in scope:

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

    • Hard line on Axiora Trades — no seed-phrase requests, period.
    • Hard line on Axiora Trades — no remote logins requested.
    • Hard line on Axiora Trades — no upfront cash retainer.
    • Hard line on Axiora Trades — no guarantee language.
    • Hard line on Axiora Trades — no unsolicited phone outreach.

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile QPBROKER — The Professor’s Note

    // FROM THE CASEFILE — QPBROKER

    The Professor opens the file on QPBROKER 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 qpbroker.com:

    • Initial deposit hashes to the QPBROKER receiving address at qpbroker.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:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    What the Professor will never do — by policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Mobatrade — The Professor’s Note

    // FROM THE CASEFILE — MOBATRADE

    Mobatrade is a casefile under reading. The deposits to mobatrade.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.

    The annotation reads — wallet trace:

    • Initial deposit hashes to the Mobatrade receiving address at mobatrade.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 — Mobatrade casefile:

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

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

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

    What the Professor tracks across Mobatrade casefiles:

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

    Lines the Professor will not cross:

    • Boundary on Mobatrade — seed phrases are off-limits.
    • Boundary on Mobatrade — remote logins are off-limits.
    • Boundary on Mobatrade — upfront cash retainers are off-limits.
    • Boundary on Mobatrade — guaranteed-recovery promises are off-limits.
    • Boundary on Mobatrade — 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

  • Office Hours on UTIP

    // FROM THE CASEFILE — UTIP

    UTIP, operating from utip.org, 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:

    • Deposit-side hashes from claimant wallets into UTIP’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 UTIP casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • UTIP’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 UTIP packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the UTIP 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. Read the UTIP submission — written go/no-go returned.
    2. Map the UTIP wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the UTIP off-ramp — endpoint counterparty identified.
    4. Build and file the UTIP recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the UTIP file — until written next steps exist.

    Chains and off-ramps the Professor follows:

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

    What is never asked of a claimant:

    • What the Professor will not do on UTIP — ask for a seed phrase.
    • What the Professor will not do on UTIP — request remote-access logins.
    • What the Professor will not do on UTIP — demand cash up front.
    • What the Professor will not do on UTIP — promise a guarantee.
    • What the Professor will not do on UTIP — 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

  • Nevixen — Annotated by the Professor

    // FROM THE CASEFILE — NEVIXEN

    Nevixen is a casefile under reading. The deposits to nevixen.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.

    The annotation reads — wallet trace:

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

    From the lectern — off-ramp identification:

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

    How a Nevixen casefile becomes a regulator-ready filing:

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

    What the Professor tracks across Nevixen casefiles:

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

    Lines the Professor will not cross:

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

  • Reading the Chain: GoldBrick Invest

    // FROM THE CASEFILE — GOLDBRICK INVEST

    When a deposit ledgered to GoldBrick Invest at goldbrick-invest.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 GoldBrick Invest:

    • Deposit-side hashes from claimant wallets into GoldBrick Invest’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.

    From the lectern — off-ramp identification:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the casefile records — chains and counterparties:

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

    Boundaries on every GoldBrick Invest casefile — never crossed:

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

    // FROM THE CASEFILE — SOLISMARKETS

    When deposits to SolisMarkets via solismarkets.co.za 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 SolisMarkets:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for SolisMarkets.
    • 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 Professor’s off-ramp note:

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

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

    What we read in a SolisMarkets casefile:

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

    What is never asked of a claimant:

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