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

Author: cryptocurrencyprof

  • Casefile Salma Markets — The Professor’s Note

    // FROM THE CASEFILE — SALMA MARKETS

    When deposits to Salma Markets via salmamarkets.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.

    Reading the wallets — Salma Markets casefile:

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

    Off-ramp map — where the funds left the chain:

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

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

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

    Reading-list — chains and exchanges in scope:

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

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: CityInv260

    // FROM THE CASEFILE — CITYINV260

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

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

    The Professor’s off-ramp note:

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

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

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

    What the on-chain reading covers:

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

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

  • Reading the Chain: UXTrades

    // FROM THE CASEFILE — UXTRADES

    When deposits to UXTrades via uxtrades.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.

    Reading the wallets — UXTrades casefile:

    • Initial deposit hashes to the UXTrades receiving address at uxtrades.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 annotation continues — off-ramp endpoint:

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

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

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

    Reading-list — chains and exchanges in scope:

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

    What the Professor will never do — by policy:

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

  • Casefile Alphaforex — The Professor’s Note

    // FROM THE CASEFILE — ALPHAFOREX

    Alphaforex is a casefile under reading. The deposits to alphaforex.eu 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 alphaforex.eu:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Alphaforex.
    • Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
    • Bridge events into chains where the operator can off-ramp at scale.
    • Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
    • Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

    Off-ramp map — where the funds left the chain:

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

    What the casefile records — chains and counterparties:

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

    Lines the Professor will not cross:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • TheWealthCore — Annotated by the Professor

    // FROM THE CASEFILE — THEWEALTHCORE

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

    • Deposit transaction hashes from the claimant wallet to the TheWealthCore 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 summary — TheWealthCore casefile:

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

    Reading-list — chains and exchanges in scope:

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

    Lines we never cross — by published policy:

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

  • Reading the Chain: Live Trade FX

    // FROM THE CASEFILE — LIVE TRADE FX

    When a deposit ledgered to Live Trade FX at livetradefx.live 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:

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

    Off-ramp map — where the funds left the chain:

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

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

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

    Reading-list — chains and exchanges in scope:

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

    Lines the Professor will not cross:

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

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

    // FROM THE CASEFILE — BITRADEINDEX

    The Professor opens the file on BITRADEINDEX 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 BITRADEINDEX.
    • 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:

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

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

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

    What the on-chain reading covers:

    • Chains the Professor reads for BITRADEINDEX casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
    • Off-ramps named in BITRADEINDEX — major centralised venues with compliance desks that accept regulator-grade packets.
    • Filing pathways available on BITRADEINDEX — 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:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: UOBE FX

    // FROM THE CASEFILE — UOBE FX

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

    From the marginalia — the deposit pathway:

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

    From the lectern — off-ramp identification:

    • Off-ramp endpoint for UOBE FX resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • UOBE FX’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for UOBE FX is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the UOBE FX 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. Casefile review on UOBE FX — reading the submission against the no-go list.
    2. Trace mapping on UOBE FX — pathway documented to chain-of-custody standard.
    3. Off-ramp naming on UOBE FX — exchange endpoint identified.
    4. Packet filing on UOBE FX — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
    5. Documented follow-through on UOBE FX.

    Chains and off-ramps the Professor follows:

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

    What the Professor will never do — by policy:

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

    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

  • Reading the Chain: CustodianX

    // FROM THE CASEFILE — CUSTODIANX

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

    The annotation reads — wallet trace:

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

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

    The Professor’s recovery note for CustodianX:

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

    What we read in a CustodianX casefile:

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

    Lines the Professor will not cross:

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

    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

  • Casefile Xtrade — The Professor’s Note

    // FROM THE CASEFILE — XTRADE

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

    From the marginalia — the deposit pathway:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Xtrade.
    • Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
    • Bridge events into chains where the operator can off-ramp at scale.
    • Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
    • Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

    The Professor’s off-ramp note:

    • Xtrade off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Xtrade 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 Xtrade — the packet meets the off-ramp’s published compliance standard.
    • When the Xtrade 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. Casefile review on Xtrade — reading the submission against the no-go list.
    2. Trace mapping on Xtrade — pathway documented to chain-of-custody standard.
    3. Off-ramp naming on Xtrade — exchange endpoint identified.
    4. Packet filing on Xtrade — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
    5. Documented follow-through on Xtrade.

    What the on-chain reading covers:

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

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace