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

  • AGA Traders — Annotated by the Professor

    // FROM THE CASEFILE — AGA TRADERS

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

    Wallet trace — what the Professor maps:

    • Initial deposit hashes to the AGA Traders receiving address at agamarkets.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.

    From the lectern — off-ramp identification:

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

    How a AGA Traders casefile becomes a regulator-ready filing:

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

    Chains and off-ramps the Professor follows:

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

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

  • From the Lectern: Amaraa Capital

    // FROM THE CASEFILE — AMARAA CAPITAL

    Amaraa Capital, operating from amaraacapital.me, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    Reading the wallets — Amaraa Capital casefile:

    • Deposit-side hashes from claimant wallets into Amaraa Capital’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 Amaraa Capital resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Amaraa Capital’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Amaraa Capital is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Amaraa Capital 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 Amaraa Capital:

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

    What the casefile records — chains and counterparties:

    • Deposit + forwarding chains for Amaraa Capital — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
    • Off-ramps the Amaraa Capital casefile may resolve to — centralised exchanges that respond to compliance filings.
    • Filing pathways on Amaraa Capital — 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 Amaraa Capital; the Professor never does — request seed phrases.
    • Recovery scammers do these things on Amaraa Capital; the Professor never does — request remote logins.
    • Recovery scammers do these things on Amaraa Capital; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on Amaraa Capital; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on Amaraa 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

  • Professor’s Brief: HDG Markets

    // FROM THE CASEFILE — HDG MARKETS

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

    On-chain reading — wallet flow for HDG Markets:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What we read in a HDG Markets casefile:

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

    Lines we never cross — by published policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: Goldberry Co.

    // FROM THE CASEFILE — GOLDBERRY CO.

    The Professor opens the file on Goldberry Co. 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 confirmations from the claimant to Goldberry Co.’s receiving wallet at goldberryco.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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on AMDE Forex

    // FROM THE CASEFILE — AMDE FOREX

    When deposits to AMDE Forex via randomforex.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 AMDE Forex receiving address at randomforex.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.

    The Professor’s off-ramp note:

    • AMDE Forex’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 AMDE Forex off-ramp wallet against historical laundering throughput.
    • The AMDE Forex packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for AMDE Forex, 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 AMDE Forex submission — written go/no-go returned.
    2. Map the AMDE Forex wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the AMDE Forex off-ramp — endpoint counterparty identified.
    4. Build and file the AMDE Forex recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the AMDE Forex file — until written next steps exist.

    What the on-chain reading covers:

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

    Boundaries on every AMDE Forex casefile — never crossed:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on SolidusMarkets

    // FROM THE CASEFILE — SOLIDUSMARKETS

    When deposits to SolidusMarkets via solidusmarkets.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 SolidusMarkets receiving address at solidusmarkets.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.

    From the lectern — off-ramp identification:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    What is never asked of a claimant:

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

  • Reading the Chain: FXPD

    // FROM THE CASEFILE — FXPD

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

    On-chain reading — wallet flow for FXPD:

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

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

    How a FXPD casefile becomes a regulator-ready filing:

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

    What the on-chain reading covers:

    • Chains the FXPD 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 FXPD — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the FXPD 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 FXPD casefile — never request a seed phrase. Ever.
    • On the FXPD casefile — never request remote-access logins to a wallet or exchange.
    • On the FXPD casefile — never demand an upfront cash retainer to scope the matter.
    • On the FXPD casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the FXPD casefile — never call the claimant unsolicited. Written-only.

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: TheCapitalForexFx

    // FROM THE CASEFILE — THECAPITALFOREXFX

    When a deposit ledgered to TheCapitalForexFx at thecapitalforexfx.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 transaction hashes from the claimant wallet to the TheCapitalForexFx 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:

    • On the TheCapitalForexFx casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
    • The off-ramp wallet for TheCapitalForexFx is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the TheCapitalForexFx casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, TheCapitalForexFx escalates to IC3, state AG, and civil-discovery overlay.

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

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

    What the casefile records — chains and counterparties:

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

    Lines the Professor will not cross:

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

  • Casefile Parallel Investment — The Professor’s Note

    // FROM THE CASEFILE — PARALLEL INVESTMENT

    When deposits to Parallel Investment via parallelinvestment.io 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.

    From the marginalia — the deposit pathway:

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

    From the lectern — off-ramp identification:

    • On the Parallel Investment casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
    • The off-ramp wallet for Parallel Investment is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the Parallel Investment casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, Parallel Investment escalates to IC3, state AG, and civil-discovery overlay.

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

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

    Chains and off-ramps the Professor follows:

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

    What is never asked of a claimant:

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

  • SmartTop — Annotated by the Professor

    // FROM THE CASEFILE — SMARTTOP

    The Professor opens the file on SmartTop 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 SmartTop’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 SmartTop resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • SmartTop’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for SmartTop is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the SmartTop 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 SmartTop — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on SmartTop — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for SmartTop is named to a centralised exchange wallet.
    4. Packet filing on SmartTop — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with SmartTop until a documented outcome or escalation step is on file.

    Chains and off-ramps the Professor follows:

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

    What is never asked of a claimant:

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

    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