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: STOCK BASE CORP

    // FROM THE CASEFILE — STOCK BASE CORP

    When a deposit ledgered to STOCK BASE CORP at stockbase.finance 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:

    • Initial deposit hashes to the STOCK BASE CORP receiving address at stockbase.finance.
    • 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 STOCK BASE CORP:

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

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

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

    What the Professor tracks across STOCK BASE CORP casefiles:

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

    Boundaries on every STOCK BASE CORP casefile — never crossed:

    • Recovery scammers do these things on STOCK BASE CORP; the Professor never does — request seed phrases.
    • Recovery scammers do these things on STOCK BASE CORP; the Professor never does — request remote logins.
    • Recovery scammers do these things on STOCK BASE CORP; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on STOCK BASE CORP; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on STOCK BASE CORP; 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 LPL Trade — The Professor’s Note

    // FROM THE CASEFILE — LPL TRADE

    When a deposit ledgered to LPL Trade at lpltrade.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 transaction hashes from the claimant wallet to the LPL Trade 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 map — where the funds left the chain:

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

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

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

    Chains and off-ramps the Professor follows:

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

    What the Professor will never do — by policy:

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

    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: Birexmarket

    // FROM THE CASEFILE — BIREXMARKET

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

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

  • Casefile Cryptoglobafx — The Professor’s Note

    // FROM THE CASEFILE — CRYPTOGLOBAFX

    When a deposit ledgered to Cryptoglobafx at cryptoflobalfsx.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:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What we read in a Cryptoglobafx casefile:

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

    What the Professor will never do — by policy:

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

  • Aicoinstrade — Annotated by the Professor

    // FROM THE CASEFILE — AICOINSTRADE

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

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

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

    What the on-chain reading covers:

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

    Recovery scammers do these things; the Professor never does:

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

  • Reading the Chain: Expo Trust

    // FROM THE CASEFILE — EXPO TRUST

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

    Wallet trace — what the Professor maps:

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

    From the lectern — off-ramp identification:

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

    Recovery pathway — how this casefile moves toward filing:

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

    Reading-list — chains and exchanges in scope:

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

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • ABBInvest — Annotated by the Professor

    // FROM THE CASEFILE — ABBINVEST

    Funds you sent to ABBInvest (abbinvest.az) 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 ABBInvest:

    • Deposit confirmations from the claimant to ABBInvest’s receiving wallet at abbinvest.az.
    • 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 — ABBInvest casefile:

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

    Recovery pathway — how this casefile moves toward filing:

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

    Chains and off-ramps the Professor follows:

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

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

  • AvantGardeFx — Annotated by the Professor

    // FROM THE CASEFILE — AVANTGARDEFX

    Funds you sent to AvantGardeFx (avantgarde-fx.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:

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

    The annotation continues — off-ramp endpoint:

    • Endpoint counterparty in the AvantGardeFx casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • AvantGardeFx’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 AvantGardeFx packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the AvantGardeFx 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. Casefile triage on AvantGardeFx — the submission is read; a written assessment is delivered.
    2. Forensic trace on AvantGardeFx — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the AvantGardeFx endpoint is named.
    4. Recovery filing on AvantGardeFx — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of AvantGardeFx — the Professor follows the casefile until next-step documentation exists.

    What the casefile records — chains and counterparties:

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

    Boundaries on every AvantGardeFx casefile — never crossed:

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

  • EqualFX — Annotated by the Professor

    // FROM THE CASEFILE — EQUALFX

    The Professor opens the file on EqualFX 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 confirmations from the claimant to EqualFX’s receiving wallet at equalfx.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 EqualFX resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • EqualFX’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for EqualFX is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the EqualFX off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

    How a EqualFX casefile becomes a regulator-ready filing:

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    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 XTXMK

    // FROM THE CASEFILE — XTXMK

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

    Trace summary — funds that left xtxmk.com:

    • Deposit-side hashes from claimant wallets into XTXMK’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 map — where the funds left the chain:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What we read in a XTXMK casefile:

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

    Lines we never cross — by published policy:

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