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: crypto recovery

  • 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

  • Office Hours on Chainblocks

    // FROM THE CASEFILE — CHAINBLOCKS

    Chainblocks, operating from chainbl0cks.net, 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 — Chainblocks casefile:

    • Deposit confirmations from the claimant to Chainblocks’s receiving wallet at chainbl0cks.net.
    • 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:

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

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

    What the casefile records — chains and counterparties:

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

    What is never asked of a claimant:

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

  • Niagarahub.net — Annotated by the Professor

    // FROM THE CASEFILE — NIAGARAHUB.NET

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

    Trace summary — funds that left niagarahub.net:

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

    • Niagarahub.net off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Niagarahub.net 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 Niagarahub.net — the packet meets the off-ramp’s published compliance standard.
    • When the Niagarahub.net 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. Casefile triage on Niagarahub.net — the submission is read; a written assessment is delivered.
    2. Forensic trace on Niagarahub.net — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the Niagarahub.net endpoint is named.
    4. Recovery filing on Niagarahub.net — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of Niagarahub.net — the Professor follows the casefile until next-step documentation exists.

    Reading-list — chains and exchanges in scope:

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

    What the Professor will never do — by policy:

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

  • Office Hours on UP Options

    // FROM THE CASEFILE — UP OPTIONS

    When deposits to UP Options via upoptions.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.

    From the marginalia — the deposit pathway:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: Fusion Trade 247

    // FROM THE CASEFILE — FUSION TRADE 247

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

    The annotation continues — off-ramp endpoint:

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

    Reading-list — chains and exchanges in scope:

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

    Lines the Professor will not cross:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile iForexpips — The Professor’s Note

    // FROM THE CASEFILE — IFOREXPIPS

    iForexpips, operating from iforexpips.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:

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

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

    How a iForexpips casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    Lines we never cross — by published policy:

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

  • Professor’s Brief: FXECM

    // FROM THE CASEFILE — FXECM

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

    From the marginalia — the deposit pathway:

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

    The annotation continues — off-ramp endpoint:

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

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

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

    Chains and off-ramps the Professor follows:

    • Chains tracked on FXECM — 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 FXECM — named exchange counterparties with public compliance contacts.
    • Filings supported on FXECM — 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 FXECM — ask for a seed phrase.
    • What the Professor will not do on FXECM — request remote-access logins.
    • What the Professor will not do on FXECM — demand cash up front.
    • What the Professor will not do on FXECM — promise a guarantee.
    • What the Professor will not do on FXECM — 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

  • MicroxStock Ltd — Annotated by the Professor

    // FROM THE CASEFILE — MICROXSTOCK LTD

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

    On-chain reading — wallet flow for MicroxStock Ltd:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for MicroxStock Ltd.
    • 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 reading — exchange counterparty for MicroxStock Ltd:

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

    What the Professor tracks across MicroxStock Ltd casefiles:

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

    Lines the Professor will not cross:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace