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

  • Office Hours on Locked In Trading

    // FROM THE CASEFILE — LOCKED IN TRADING

    Locked In Trading, operating from lockedintrading.co, 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:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Locked In Trading.
    • 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 annotation continues — off-ramp endpoint:

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

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

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

    What the casefile records — chains and counterparties:

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

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

  • Zenith Capital — Annotated by the Professor

    // FROM THE CASEFILE — ZENITH CAPITAL

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

    Trace summary — funds that left zenithcapico.com:

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

    Off-ramp summary — Zenith Capital casefile:

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

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

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

    What the casefile records — chains and counterparties:

    • Chains the Zenith Capital 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 Zenith Capital — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the Zenith Capital 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 Zenith Capital — ask for a seed phrase.
    • What the Professor will not do on Zenith Capital — request remote-access logins.
    • What the Professor will not do on Zenith Capital — demand cash up front.
    • What the Professor will not do on Zenith Capital — promise a guarantee.
    • What the Professor will not do on Zenith Capital — 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

  • Office Hours on BullsWealth

    // FROM THE CASEFILE — BULLSWEALTH

    BullsWealth is a casefile under reading. The deposits to bullswealth.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:

    • Initial deposit hashes to the BullsWealth receiving address at bullswealth.com.
    • Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
    • Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
    • Obfuscation events through mixer contracts and privacy services.
    • Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

    Off-ramp summary — BullsWealth casefile:

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

    What the Professor tracks across BullsWealth casefiles:

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

  • Professor’s Brief: Nixars Group

    // FROM THE CASEFILE — NIXARS GROUP

    The Professor opens the file on Nixars Group 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.

    Reading the wallets — Nixars Group casefile:

    • Initial deposit hashes to the Nixars Group receiving address at nixarsgroup.com.
    • Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
    • Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
    • Obfuscation events through mixer contracts and privacy services.
    • Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

    Off-ramp summary — Nixars Group casefile:

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

    The Professor’s recovery note for Nixars Group:

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

    Chains and off-ramps the Professor follows:

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

    • Nixars Group policy — seed phrases are never requested.
    • Nixars Group policy — remote-access logins are never requested.
    • Nixars Group policy — no upfront cash retainer to scope.
    • Nixars Group policy — no guaranteed-recovery language. None.
    • Nixars Group policy — no unsolicited calls. The Professor responds in writing 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

  • From the Lectern: Sage Capital Research

    // FROM THE CASEFILE — SAGE CAPITAL RESEARCH

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

    From the marginalia — the deposit pathway:

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

    • Sage Capital Research’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 Sage Capital Research off-ramp wallet against historical laundering throughput.
    • The Sage Capital Research packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for Sage Capital Research, 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 Sage Capital Research — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on Sage Capital Research — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for Sage Capital Research is named to a centralised exchange wallet.
    4. Packet filing on Sage Capital Research — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with Sage Capital Research until a documented outcome or escalation step is on file.

    What we read in a Sage Capital Research casefile:

    • Deposit-side chains in Sage Capital Research 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 Sage Capital Research packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Sage Capital Research — 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:

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

  • Office Hours on DCEX

    // FROM THE CASEFILE — DCEX

    When a deposit ledgered to DCEX at dcexbas.vip 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 DCEX:

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

    From the lectern — off-ramp identification:

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

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

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

    Chains and off-ramps the Professor follows:

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

    Recovery scammers do these things; the Professor never does:

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

  • Reading the Chain: ECCapital

    // FROM THE CASEFILE — ECCAPITAL

    Funds you sent to ECCapital (eccapitals.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.

    The annotation reads — wallet trace:

    • Initial deposit hashes to the ECCapital receiving address at eccapitals.com.
    • Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
    • Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
    • Obfuscation events through mixer contracts and privacy services.
    • Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

    Off-ramp summary — ECCapital casefile:

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

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

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

    What the casefile records — chains and counterparties:

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

    What the Professor will never do — by policy:

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

  • Reading the Chain: Tag Markets

    // FROM THE CASEFILE — TAG MARKETS

    The Professor opens the file on Tag Markets 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.

    Reading the wallets — Tag Markets casefile:

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

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

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

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

    Reading-list — chains and exchanges in scope:

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

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

  • From the Lectern: NewFX

    // FROM THE CASEFILE — NEWFX

    Funds you sent to NewFX (newfx.us) 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.

    Reading the wallets — NewFX casefile:

    • Initial deposit hashes to the NewFX receiving address at newfx.us.
    • Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
    • Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
    • Obfuscation events through mixer contracts and privacy services.
    • Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

    Off-ramp summary — NewFX casefile:

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

    The Professor’s recovery note for NewFX:

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

    What we read in a NewFX casefile:

    • Chains the NewFX 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 NewFX — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the NewFX 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 NewFX; the Professor never does — request seed phrases.
    • Recovery scammers do these things on NewFX; the Professor never does — request remote logins.
    • Recovery scammers do these things on NewFX; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on NewFX; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on NewFX; the Professor never does — call you unsolicited.

    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 Bakkt Market

    // FROM THE CASEFILE — BAKKT MARKET

    Bakkt Market, operating from webullforex.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 Bakkt Market:

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

    The Professor’s off-ramp note:

    • Bakkt Market’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 Bakkt Market off-ramp wallet against historical laundering throughput.
    • The Bakkt Market packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for Bakkt Market, 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. First read on Bakkt Market — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on Bakkt Market — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for Bakkt Market is named to a centralised exchange wallet.
    4. Packet filing on Bakkt Market — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with Bakkt Market until a documented outcome or escalation step is on file.

    What the Professor tracks across Bakkt Market casefiles:

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

    Lines the Professor will not cross:

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