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: get stolen crypto back

  • Professor’s Brief: FOGO

    // FROM THE CASEFILE — FOGO

    FOGO is a casefile under reading. The deposits to fogoforex.com sit on-chain, immutable; the wallet pathway is the primary source, and the off-ramp endpoint is the conclusion the Professor’s marginalia points toward.

    From the marginalia — the deposit pathway:

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

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

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

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

    Reading-list — chains and exchanges in scope:

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

    Boundaries on every FOGO casefile — never crossed:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on AITrader

    // FROM THE CASEFILE — AITRADER

    AITrader is a casefile under reading. The deposits to aitrader.fm 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.

    Wallet trace — what the Professor maps:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for AITrader.
    • Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
    • Bridge events into chains where the operator can off-ramp at scale.
    • Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
    • Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

    Off-ramp map — where the funds left the chain:

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

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

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

    What the on-chain reading covers:

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

    What is never asked of a claimant:

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

  • Professor’s Brief: L2P Brokerage

    // FROM THE CASEFILE — L2P BROKERAGE

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

    Trace summary — funds that left leads2performancebrokerage.com:

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

    Off-ramp summary — L2P Brokerage casefile:

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

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

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

    What the on-chain reading covers:

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

    Recovery scammers do these things; the Professor never does:

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

  • Scp group ltd — Annotated by the Professor

    // FROM THE CASEFILE — SCP GROUP LTD

    Scp group ltd, operating from scpcndhcfv.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 Scp group ltd:

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

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

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

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

    What the Professor tracks across Scp group ltd casefiles:

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

    Lines we never cross — by published policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Sugexcryptopro — The Professor’s Note

    // FROM THE CASEFILE — SUGEXCRYPTOPRO

    Sugexcryptopro is a casefile under reading. The deposits to sugexcryptopro.net 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 sugexcryptopro.net:

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

    • Sugexcryptopro’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 Sugexcryptopro off-ramp wallet against historical laundering throughput.
    • The Sugexcryptopro packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for Sugexcryptopro, 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 Sugexcryptopro — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on Sugexcryptopro — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for Sugexcryptopro is named to a centralised exchange wallet.
    4. Packet filing on Sugexcryptopro — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with Sugexcryptopro until a documented outcome or escalation step is on file.

    Chains and off-ramps the Professor follows:

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

    Lines the Professor will not cross:

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

  • Casefile Fake Forthright — The Professor’s Note

    // FROM THE CASEFILE — FAKE FORTHRIGHT

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

    The annotation reads — wallet trace:

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

    • Fake Forthright 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 Forthright 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 Forthright — the packet meets the off-ramp’s published compliance standard.
    • When the Fake Forthright 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. Read the Fake Forthright submission — written go/no-go returned.
    2. Map the Fake Forthright wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the Fake Forthright off-ramp — endpoint counterparty identified.
    4. Build and file the Fake Forthright recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the Fake Forthright file — until written next steps exist.

    What the Professor tracks across Fake Forthright casefiles:

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

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

    Open a free first consultation — /contact-us/ — written response within one business day.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Clone Vernier Capital Advisors — Annotated by the Professor

    // FROM THE CASEFILE — CLONE VERNIER CAPITAL ADVISORS

    Clone Vernier Capital Advisors is a casefile under reading. The deposits to verniercapitaladvisors.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.

    Reading the wallets — Clone Vernier Capital Advisors casefile:

    • Deposit confirmations from the claimant to Clone Vernier Capital Advisors’s receiving wallet at verniercapitaladvisors.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 map — where the funds left the chain:

    • Off-ramp endpoint for Clone Vernier Capital Advisors resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Clone Vernier Capital Advisors’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Clone Vernier Capital Advisors is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Clone Vernier Capital Advisors 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. Submission triage — Clone Vernier Capital Advisors casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — Clone Vernier Capital Advisors deposit and forwarding wallets captured.
    3. Endpoint identification — Clone Vernier Capital Advisors off-ramp wallet named.
    4. Filing — Clone Vernier Capital Advisors packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — Clone Vernier Capital Advisors stays on file until a documented next step is reached.

    What the Professor tracks across Clone Vernier Capital Advisors casefiles:

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

    Lines we never cross — by published policy:

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

  • Reading the Chain: Ortega Capital Limited

    // FROM THE CASEFILE — ORTEGA CAPITAL LIMITED

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

    From the marginalia — the deposit pathway:

    • Deposit transaction hashes from the claimant wallet to the Ortega Capital Limited 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 summary — Ortega Capital Limited casefile:

    • Endpoint counterparty in the Ortega Capital Limited casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Ortega Capital Limited’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 Ortega Capital Limited packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Ortega Capital Limited 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. Triage on Ortega Capital Limited — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on Ortega Capital Limited — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on Ortega Capital Limited — off-ramp endpoint matched to a named exchange counterparty.
    4. File the Ortega Capital Limited 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 Ortega Capital Limited — the Professor stays on the casefile until a documented next step exists.

    Reading-list — chains and exchanges in scope:

    • Chains the Ortega Capital 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 Ortega Capital Limited — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the Ortega Capital 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 Ortega Capital Limited; the Professor never does — request seed phrases.
    • Recovery scammers do these things on Ortega Capital Limited; the Professor never does — request remote logins.
    • Recovery scammers do these things on Ortega Capital Limited; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on Ortega Capital Limited; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on Ortega Capital Limited; 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

  • From the Lectern: Maxus Global Market

    // FROM THE CASEFILE — MAXUS GLOBAL MARKET

    Maxus Global Market is a casefile under reading. The deposits to maxusfex.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.

    Wallet trace — what the Professor maps:

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

    • Maxus Global Market off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Maxus Global Market 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 Maxus Global Market — the packet meets the off-ramp’s published compliance standard.
    • When the Maxus Global Market 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 review on Maxus Global Market — reading the submission against the no-go list.
    2. Trace mapping on Maxus Global Market — pathway documented to chain-of-custody standard.
    3. Off-ramp naming on Maxus Global Market — exchange endpoint identified.
    4. Packet filing on Maxus Global Market — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
    5. Documented follow-through on Maxus Global Market.

    What we read in a Maxus Global Market casefile:

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

    What is never asked of a claimant:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • COINEXX — Annotated by the Professor

    // FROM THE CASEFILE — COINEXX

    When a deposit ledgered to COINEXX at coinexx.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 deposit hashes — provided in the case submission and verified against the public ledger for COINEXX.
    • Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
    • Bridge events into chains where the operator can off-ramp at scale.
    • Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
    • Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

    Off-ramp summary — COINEXX casefile:

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

    The Professor’s recovery note for COINEXX:

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

    What the on-chain reading covers:

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

    What is never asked of a claimant:

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