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 →

Tag: report a scam

  • Casefile EQFX Trade — The Professor’s Note

    // FROM THE CASEFILE — EQFX TRADE

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

    From the marginalia — the deposit pathway:

    • Deposit confirmations from the claimant to EQFX Trade’s receiving wallet at eqfx.trade.
    • 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:

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

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

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

    What we read in a EQFX Trade casefile:

    • Chains the Professor reads for EQFX Trade casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
    • Off-ramps named in EQFX Trade — major centralised venues with compliance desks that accept regulator-grade packets.
    • Filing pathways available on EQFX Trade — 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 EQFX Trade — ask for a seed phrase.
    • What the Professor will not do on EQFX Trade — request remote-access logins.
    • What the Professor will not do on EQFX Trade — demand cash up front.
    • What the Professor will not do on EQFX Trade — promise a guarantee.
    • What the Professor will not do on EQFX Trade — call you out of the blue.

    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 Brokercap CFD24 — The Professor’s Note

    // FROM THE CASEFILE — BROKERCAP CFD24

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

    Wallet trace — what the Professor maps:

    • Deposit confirmations from the claimant to Brokercap CFD24’s receiving wallet at brokercapcfd24.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.

    From the lectern — off-ramp identification:

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

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

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

    What we read in a Brokercap CFD24 casefile:

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

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Cudrania Capital

    // FROM THE CASEFILE — CUDRANIA CAPITAL

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

    The annotation reads — wallet trace:

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

    • Endpoint counterparty in the Cudrania Capital casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Cudrania Capital’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
    • Leverage is applied to that named counterparty — the Cudrania Capital packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Cudrania Capital off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

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

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

    What we read in a Cudrania Capital casefile:

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

    Lines we never cross — by published policy:

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

  • From the Lectern: FX CRYP LAND

    // FROM THE CASEFILE — FX CRYP LAND

    When deposits to FX CRYP LAND via fxcrypland.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.

    Wallet trace — what the Professor maps:

    • Deposit-side hashes from claimant wallets into FX CRYP LAND’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:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Lines the Professor will not cross:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile FreeFxTrade — The Professor’s Note

    // FROM THE CASEFILE — FREEFXTRADE

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

    From the marginalia — the deposit pathway:

    • Deposit confirmations from the claimant to FreeFxTrade’s receiving wallet at freefxtrade.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 reading — exchange counterparty for FreeFxTrade:

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

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

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

    Chains and off-ramps the Professor follows:

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

    Boundaries on every FreeFxTrade casefile — never crossed:

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

  • SPG — Annotated by the Professor

    // FROM THE CASEFILE — SPG

    SPG is a casefile under reading. The deposits to spgzeds.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.

    From the marginalia — the deposit pathway:

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

    • SPG’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 SPG off-ramp wallet against historical laundering throughput.
    • The SPG packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for SPG, 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. Submission triage — SPG casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — SPG deposit and forwarding wallets captured.
    3. Endpoint identification — SPG off-ramp wallet named.
    4. Filing — SPG packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — SPG stays on file until a documented next step is reached.

    Chains and off-ramps the Professor follows:

    • Chains the SPG 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 SPG — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the SPG 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 SPG — no seed-phrase requests, period.
    • Hard line on SPG — no remote logins requested.
    • Hard line on SPG — no upfront cash retainer.
    • Hard line on SPG — no guarantee language.
    • Hard line on SPG — no unsolicited phone outreach.

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Clone NSFX — The Professor’s Note

    // FROM THE CASEFILE — CLONE NSFX

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

    On-chain reading — wallet flow for Clone NSFX:

    • Deposit-side hashes from claimant wallets into Clone NSFX’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 reading — exchange counterparty for Clone NSFX:

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

    Recovery pathway — how this casefile moves toward filing:

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

    Reading-list — chains and exchanges in scope:

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

    What the Professor will never do — by policy:

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

  • INCOGAIN — Annotated by the Professor

    // FROM THE CASEFILE — INCOGAIN

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

    On-chain reading — wallet flow for INCOGAIN:

    • Deposit-side hashes from claimant wallets into INCOGAIN’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:

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

    The Professor’s recovery note for INCOGAIN:

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

    Chains and off-ramps the Professor follows:

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

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Revolution FSL

    // FROM THE CASEFILE — REVOLUTION FSL

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

    From the marginalia — the deposit pathway:

    • Deposit confirmations from the claimant to Revolution FSL’s receiving wallet at revolutionfsl.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 reading — exchange counterparty for Revolution FSL:

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

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

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

    What the on-chain reading covers:

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

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

  • Office Hours on FxMatrix

    // FROM THE CASEFILE — FXMATRIX

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

    On-chain reading — wallet flow for FxMatrix:

    • Deposit confirmations from the claimant to FxMatrix’s receiving wallet at fxmatrix.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.

    Off-ramp reading — exchange counterparty for FxMatrix:

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

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

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

    What the Professor tracks across FxMatrix casefiles:

    • Chains the Professor reads for FxMatrix casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
    • Off-ramps named in FxMatrix — major centralised venues with compliance desks that accept regulator-grade packets.
    • Filing pathways available on FxMatrix — 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 FxMatrix — no seed-phrase requests, period.
    • Hard line on FxMatrix — no remote logins requested.
    • Hard line on FxMatrix — no upfront cash retainer.
    • Hard line on FxMatrix — no guarantee language.
    • Hard line on FxMatrix — 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