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

Category: Scam Brokers

Annotated readings of brokers and platforms the Cryptocurrency Professor has documented.

  • Professor’s Brief: Capitus

    // FROM THE CASEFILE — CAPITUS

    The Professor opens the file on Capitus 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:

    • Initial deposit hashes to the Capitus receiving address at capitus.net.
    • 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:

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

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

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

    Chains and off-ramps the Professor follows:

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

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

  • From the Lectern: TeamStar Fx

    // FROM THE CASEFILE — TEAMSTAR FX

    The Professor opens the file on TeamStar Fx 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 teamstarforex.com:

    • Initial deposit hashes to the TeamStar Fx receiving address at teamstarforex.com.
    • Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
    • Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
    • Obfuscation events through mixer contracts and privacy services.
    • Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

    Off-ramp reading — exchange counterparty for TeamStar Fx:

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

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

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

    What the casefile records — chains and counterparties:

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

    What the Professor will never do — by policy:

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

    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

  • AMCHUNKS — Annotated by the Professor

    // FROM THE CASEFILE — AMCHUNKS

    Funds you sent to AMCHUNKS (amchunks.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 amchunks.com:

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

    The Professor’s off-ramp note:

    • AMCHUNKS’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 AMCHUNKS off-ramp wallet against historical laundering throughput.
    • The AMCHUNKS packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for AMCHUNKS, 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. Triage on AMCHUNKS — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on AMCHUNKS — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on AMCHUNKS — off-ramp endpoint matched to a named exchange counterparty.
    4. File the AMCHUNKS 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 AMCHUNKS — the Professor stays on the casefile until a documented next step exists.

    Reading-list — chains and exchanges in scope:

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

    Lines we never cross — by published policy:

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

  • ZENITH GLOBAL VENTURE — Annotated by the Professor

    // FROM THE CASEFILE — ZENITH GLOBAL VENTURE

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

    Wallet trace — what the Professor maps:

    • Deposit confirmations from the claimant to ZENITH GLOBAL VENTURE’s receiving wallet at zenithglobalventure.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:

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

    The Professor’s recovery note for ZENITH GLOBAL VENTURE:

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

    What the on-chain reading covers:

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

    Boundaries on every ZENITH GLOBAL VENTURE casefile — never crossed:

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

  • Reading the Chain: CrudeXcoins

    // FROM THE CASEFILE — CRUDEXCOINS

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

    From the marginalia — the deposit pathway:

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

    From the lectern — off-ramp identification:

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

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

    What the Professor tracks across CrudeXcoins casefiles:

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

    Boundaries on every CrudeXcoins casefile — never crossed:

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

    // FROM THE CASEFILE — GIRAFFE MARKETS

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

    The annotation reads — wallet trace:

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

    Off-ramp summary — Giraffe Markets casefile:

    • Giraffe Markets’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage — typically named in the packet alongside the deposit address.
    • Chain-analytics datasets cross-reference the Giraffe Markets off-ramp wallet against historical laundering throughput.
    • The Giraffe Markets packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for Giraffe Markets, 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. Read the Giraffe Markets submission — written go/no-go returned.
    2. Map the Giraffe Markets wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the Giraffe Markets off-ramp — endpoint counterparty identified.
    4. Build and file the Giraffe Markets recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the Giraffe Markets file — until written next steps exist.

    Reading-list — chains and exchanges in scope:

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

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: Brisk Markets

    // FROM THE CASEFILE — BRISK MARKETS

    The Professor opens the file on Brisk Markets 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:

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

    The Professor’s off-ramp note:

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

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

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

    Chains and off-ramps the Professor follows:

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

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Professor’s Brief: Square Markets

    // FROM THE CASEFILE — SQUARE MARKETS

    Funds you sent to Square Markets (squaremarkets.net) 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:

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

    From the lectern — off-ramp identification:

    • Square Markets’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage — typically named in the packet alongside the deposit address.
    • Chain-analytics datasets cross-reference the Square Markets off-ramp wallet against historical laundering throughput.
    • The Square Markets packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for Square Markets, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

    How a Square Markets casefile becomes a regulator-ready filing:

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

    What the Professor tracks across Square Markets casefiles:

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

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

  • From the Lectern: Fordshirax

    // FROM THE CASEFILE — FORDSHIRAX

    The Professor opens the file on Fordshirax 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:

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

    The annotation continues — off-ramp endpoint:

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

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

    What the casefile records — chains and counterparties:

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

    Recovery scammers do these things; the Professor never does:

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

  • StockValo — Annotated by the Professor

    // FROM THE CASEFILE — STOCKVALO

    When deposits to StockValo via stockvalo.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-side hashes from claimant wallets into StockValo’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 — StockValo casefile:

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

    How a StockValo casefile becomes a regulator-ready filing:

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

    What the Professor tracks across StockValo casefiles:

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

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

    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