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

Tag: scam help

  • Office Hours on CLICKFXM

    // FROM THE CASEFILE — CLICKFXM

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

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

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

    How a CLICKFXM casefile becomes a regulator-ready filing:

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

    What the casefile records — chains and counterparties:

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

    What is never asked of a claimant:

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

  • Casefile Targon AG — The Professor’s Note

    // FROM THE CASEFILE — TARGON AG

    Funds you sent to Targon AG (targon.ltd) 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 Targon AG:

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

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

    What the casefile records — chains and counterparties:

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

    What is never asked of a claimant:

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

    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 GCMAsia

    // FROM THE CASEFILE — GCMASIA

    When deposits to GCMAsia via gcmasia.com go quiet, the on-chain record stays loud. The Professor’s reading begins where the platform’s silence does — with the wallet that received the funds and the path it took afterward.

    The annotation reads — wallet trace:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Recovery scammers do these things; the Professor never does:

    • Recovery scammers do these things on GCMAsia; the Professor never does — request seed phrases.
    • Recovery scammers do these things on GCMAsia; the Professor never does — request remote logins.
    • Recovery scammers do these things on GCMAsia; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on GCMAsia; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on GCMAsia; 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

  • Professor’s Brief: Trade Next Generation

    // FROM THE CASEFILE — TRADE NEXT GENERATION

    When deposits to Trade Next Generation via tradenextgen.org 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.

    Trace summary — funds that left tradenextgen.org:

    • Deposit confirmations from the claimant to Trade Next Generation’s receiving wallet at tradenextgen.org.
    • 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:

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

    The Professor’s recovery note for Trade Next Generation:

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

    What the Professor tracks across Trade Next Generation casefiles:

    • Deposit-side chains in Trade Next Generation 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 Trade Next Generation packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Trade Next Generation — 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 Trade Next Generation casefile — never request a seed phrase. Ever.
    • On the Trade Next Generation casefile — never request remote-access logins to a wallet or exchange.
    • On the Trade Next Generation casefile — never demand an upfront cash retainer to scope the matter.
    • On the Trade Next Generation casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the Trade Next Generation casefile — never call the claimant unsolicited. Written-only.

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Profix Capital — The Professor’s Note

    // FROM THE CASEFILE — PROFIX CAPITAL

    Profix Capital, operating from profixcapital.com, 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 Profix Capital:

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

    The annotation continues — off-ramp endpoint:

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

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

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

    What we read in a Profix Capital casefile:

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

    Lines the Professor will not cross:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Aggregate Trading — Annotated by the Professor

    // FROM THE CASEFILE — AGGREGATE TRADING

    When deposits to Aggregate Trading via aggrefx.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 — Aggregate Trading casefile:

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

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

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

    What the on-chain reading covers:

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

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Professor’s Brief: Fiber Markets

    // FROM THE CASEFILE — FIBER MARKETS

    When deposits to Fiber Markets via fibermarkets.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:

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

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

    How a Fiber Markets casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: RuiGenFuTou

    // FROM THE CASEFILE — RUIGENFUTOU

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

    The annotation reads — wallet trace:

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

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

    Reading-list — chains and exchanges in scope:

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

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • NAB Crypto — Annotated by the Professor

    // FROM THE CASEFILE — NAB CRYPTO

    When deposits to NAB Crypto via nabcrypto.io go quiet, the on-chain record stays loud. The Professor’s reading begins where the platform’s silence does — with the wallet that received the funds and the path it took afterward.

    On-chain reading — wallet flow for NAB Crypto:

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

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

    What we read in a NAB Crypto casefile:

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

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

    // FROM THE CASEFILE — FAKE FXCM

    When a deposit ledgered to Fake FXCM at global-fh.com;https: 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 Fake FXCM:

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

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

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

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

    What the Professor tracks across Fake FXCM casefiles:

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

    Lines the Professor will not cross:

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