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

Tag: investment scam

  • Hiltonmetafx — Annotated by the Professor

    // FROM THE CASEFILE — HILTONMETAFX

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

    On-chain reading — wallet flow for Hiltonmetafx:

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

    Off-ramp summary — Hiltonmetafx casefile:

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

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

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

    What we read in a Hiltonmetafx casefile:

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

    Lines the Professor will not cross:

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

  • Professor’s Brief: Nexusglobalmarket

    // FROM THE CASEFILE — NEXUSGLOBALMARKET

    Funds you sent to Nexusglobalmarket (nexusglobalmarket.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 confirmations from the claimant to Nexusglobalmarket’s receiving wallet at nexusglobalmarket.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 — Nexusglobalmarket casefile:

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

    The Professor’s recovery note for Nexusglobalmarket:

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

    What we read in a Nexusglobalmarket casefile:

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

    Boundaries on every Nexusglobalmarket casefile — never crossed:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile CONFIDENCIAL FXMARKETS — The Professor’s Note

    // FROM THE CASEFILE — CONFIDENCIAL FXMARKETS

    Funds you sent to CONFIDENCIAL FXMARKETS (confidencialfxmarkets.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 CONFIDENCIAL FXMARKETS:

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

    Off-ramp reading — exchange counterparty for CONFIDENCIAL FXMARKETS:

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

    What the Professor tracks across CONFIDENCIAL FXMARKETS casefiles:

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

    Lines the Professor will not cross:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: Net Fx Miner

    // FROM THE CASEFILE — NET FX MINER

    The Professor opens the file on Net Fx Miner 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 Net Fx Miner receiving address at netfxminer.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 map — where the funds left the chain:

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

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

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

    What the on-chain reading covers:

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

    Recovery scammers do these things; the Professor never does:

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

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

    // FROM THE CASEFILE — PRIMEDELTAS

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

    From the marginalia — the deposit pathway:

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

    • Off-ramp endpoint for PrimeDeltas resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • PrimeDeltas’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for PrimeDeltas is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the PrimeDeltas 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. Triage on PrimeDeltas — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on PrimeDeltas — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on PrimeDeltas — off-ramp endpoint matched to a named exchange counterparty.
    4. File the PrimeDeltas 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 PrimeDeltas — the Professor stays on the casefile until a documented next step exists.

    What the casefile records — chains and counterparties:

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

    What is never asked of a claimant:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: ABZ Capital

    // FROM THE CASEFILE — ABZ CAPITAL

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

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

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

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

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

    What the on-chain reading covers:

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

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on spencerandstanley.com

    // FROM THE CASEFILE — SPENCERANDSTANLEY.COM

    When deposits to spencerandstanley.com via spencerandstanley.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:

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

    Off-ramp summary — spencerandstanley.com casefile:

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

    The Professor’s recovery note for spencerandstanley.com:

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

    Chains and off-ramps the Professor follows:

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

    Lines the Professor will not cross:

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

  • Professor’s Brief: Above Capital

    // FROM THE CASEFILE — ABOVE CAPITAL

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

    Wallet trace — what the Professor maps:

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

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

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

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

    What we read in a Above Capital casefile:

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

    Lines we never cross — by published policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile BitPania — The Professor’s Note

    // FROM THE CASEFILE — BITPANIA

    Funds you sent to BitPania (bitpania.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:

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

    Off-ramp summary — BitPania casefile:

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

    How a BitPania casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    What is never asked of a claimant:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: 99FX

    // FROM THE CASEFILE — 99FX

    Funds you sent to 99FX (99fx.co) 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 99fx.co:

    • Initial deposit hashes to the 99FX receiving address at 99fx.co.
    • 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 map — where the funds left the chain:

    • Endpoint counterparty in the 99FX casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • 99FX’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 99FX packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the 99FX 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. Submission triage — 99FX casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — 99FX deposit and forwarding wallets captured.
    3. Endpoint identification — 99FX off-ramp wallet named.
    4. Filing — 99FX packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — 99FX stays on file until a documented next step is reached.

    What the casefile records — chains and counterparties:

    • Chains the Professor reads for 99FX casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
    • Off-ramps named in 99FX — major centralised venues with compliance desks that accept regulator-grade packets.
    • Filing pathways available on 99FX — 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 99FX; the Professor never does — request seed phrases.
    • Recovery scammers do these things on 99FX; the Professor never does — request remote logins.
    • Recovery scammers do these things on 99FX; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on 99FX; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on 99FX; 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