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: recover stolen crypto

  • Casefile SchubKapitals — The Professor’s Note

    // FROM THE CASEFILE — SCHUBKAPITALS

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

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What we read in a SchubKapitals casefile:

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

    What is never asked of a claimant:

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

  • Office Hours on Torvex Finance

    // FROM THE CASEFILE — CTK NETWORK

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

    Trace summary — funds that left this platform:

    • Deposit confirmations from the claimant to Torvex Finance’s receiving wallet at this platform.
    • 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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Why this platform is on our casefile

    Torvex Finance has been flagged as a Fraudulent online trading platforms by FSMA Belgium. FSMA warning 30/06/2026. Jurisdiction: BE. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.fsma.be/en/warnings/companies-operating-unlawfully-in-belgium

  • Reading the Chain: Bitvest Global

    // FROM THE CASEFILE — BITVEST GLOBAL

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

    The annotation reads — wallet trace:

    • Deposit confirmations from the claimant to Bitvest Global’s receiving wallet at bitvestglobal.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 reading — exchange counterparty for Bitvest Global:

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

    How a Bitvest Global casefile becomes a regulator-ready filing:

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

    What the on-chain reading covers:

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

    Lines the Professor will not cross:

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

  • Office Hours on Trinity Hedge

    // FROM THE CASEFILE — TRINITY HEDGE

    The Professor opens the file on Trinity Hedge the same way every casefile is opened — by treating the wallet history as text and the off-ramp endpoint as the citation a regulator can verify.

    From the marginalia — the deposit pathway:

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

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

    What we read in a Trinity Hedge casefile:

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

    Lines the Professor will not cross:

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

    // FROM THE CASEFILE — FIVESTARPIPS

    When deposits to Fivestarpips via fivestarpips.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.

    The annotation reads — wallet trace:

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

    The Professor’s off-ramp note:

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

    How a Fivestarpips casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    What is never asked of a claimant:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • ATGForex — Annotated by the Professor

    // FROM THE CASEFILE — ATGFOREX

    ATGForex, operating from atgforex.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 ATGForex:

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

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

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

    Chains and off-ramps the Professor follows:

    • Deposit-side chains in ATGForex 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 ATGForex packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on ATGForex — 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:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Professor’s Brief: GAEA

    // FROM THE CASEFILE — GAEA

    Funds you sent to GAEA (gaeainvestment.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 GAEA:

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

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

    How a GAEA casefile becomes a regulator-ready filing:

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

    What the on-chain reading covers:

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

    Lines the Professor will not cross:

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

    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

  • Reading the Chain: Core-Invest

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Core-Invest via this platform 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 Core-Invest:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

    Why this platform is on our casefile

    Core-Invest has been flagged as a Fraudulent online trading platforms by FSMA Belgium. FSMA warning 18/12/2025. Jurisdiction: BE. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.fsma.be/en/warnings/companies-operating-unlawfully-in-belgium

  • Reading the Chain: Pace Capital Fx

    // FROM THE CASEFILE — PACE CAPITAL FX

    Funds you sent to Pace Capital Fx (pacecapitalfx.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.

    From the marginalia — the deposit pathway:

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

    Off-ramp reading — exchange counterparty for Pace Capital Fx:

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

    How a Pace Capital Fx casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    What is never asked of a claimant:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Bull Sphere

    // FROM THE CASEFILE — BULL SPHERE

    Bull Sphere, operating from bullsphere.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:

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

    The Professor’s off-ramp note:

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

    What we read in a Bull Sphere casefile:

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

    Boundaries on every Bull Sphere casefile — never crossed:

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