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

Tag: scam broker

  • Office Hours on AlphaReturns

    // FROM THE CASEFILE — ALPHARETURNS

    When deposits to AlphaReturns via alphareturns.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.

    The annotation reads — wallet trace:

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

    From the lectern — off-ramp identification:

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

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

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

    What we read in a AlphaReturns casefile:

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

    What the Professor will never do — by policy:

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

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

    // FROM THE CASEFILE — CENTRALTRADINGHUB

    Funds you sent to CentralTradingHub (centraltradinghub.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.

    Wallet trace — what the Professor maps:

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

    • Endpoint counterparty in the CentralTradingHub casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • CentralTradingHub’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 CentralTradingHub packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the CentralTradingHub off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

    Recovery pathway — how this casefile moves toward filing:

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

    What the casefile records — chains and counterparties:

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

    What is never asked of a claimant:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: Orvian Trade

    // FROM THE CASEFILE — ORVIAN TRADE

    When deposits to Orvian Trade via orviantrade.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 confirmations from the claimant to Orvian Trade’s receiving wallet at orviantrade.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:

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

    The Professor’s recovery note for Orvian Trade:

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

    Chains and off-ramps the Professor follows:

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

    What is never asked of a claimant:

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

  • Office Hours on McKinney Capital Partners

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to McKinney Capital Partners via mckinneycapitalpartners.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.

    Trace summary — funds that left mckinneycapitalpartners.com:

    • Deposit confirmations from the claimant to McKinney Capital Partners’s receiving wallet at mckinneycapitalpartners.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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Why this platform is on our casefile

    McKinney Capital Partners has been flagged as a fake broker/platform by IOSCO I-SCAN (United States of America – Securities and Exchange Commission). reported 2026-06-04. Jurisdiction: United States of America. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.iosco.org/i-scan/

  • Office Hours on Tradeactive

    // FROM THE CASEFILE — TRADEACTIVE

    When deposits to Tradeactive via tradeactive.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:

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

    The annotation continues — off-ramp endpoint:

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

    The Professor’s recovery note for Tradeactive:

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

    Reading-list — chains and exchanges in scope:

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

    Lines the Professor will not cross:

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

  • Reading the Chain: RobinTrov

    // FROM THE CASEFILE — ROBINTROV

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

    Trace summary — funds that left robintrov.com:

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

    • RobinTrov’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 RobinTrov off-ramp wallet against historical laundering throughput.
    • The RobinTrov packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for RobinTrov, 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. Casefile review on RobinTrov — reading the submission against the no-go list.
    2. Trace mapping on RobinTrov — pathway documented to chain-of-custody standard.
    3. Off-ramp naming on RobinTrov — exchange endpoint identified.
    4. Packet filing on RobinTrov — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
    5. Documented follow-through on RobinTrov.

    What the on-chain reading covers:

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

    Boundaries on every RobinTrov casefile — never crossed:

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

    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

  • Casefile BFTCapitals (BFTCapitalspro) — The Professor’s Note

    // FROM THE CASEFILE — BFTCAPITALS (BFTCAPITALSPRO)

    When a deposit ledgered to BFTCapitals (BFTCapitalspro) at bftcapitalspro.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 bftcapitalspro.com:

    • Initial deposit hashes to the BFTCapitals (BFTCapitalspro) receiving address at bftcapitalspro.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 — BFTCapitals (BFTCapitalspro) casefile:

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

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

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

    Reading-list — chains and exchanges in scope:

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

    Recovery scammers do these things; the Professor never does:

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

    // FROM THE CASEFILE — PAXFOREX

    PaxForex, operating from paxforex.org, 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:

    • Initial deposit hashes to the PaxForex receiving address at paxforex.org.
    • 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 reading — exchange counterparty for PaxForex:

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

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

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

    Reading-list — chains and exchanges in scope:

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

    What the Professor will never do — by policy:

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

  • Reading the Chain: Quyen

    // FROM THE CASEFILE — QUYEN

    When a deposit ledgered to Quyen at quyentmarkets.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 quyentmarkets.com:

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

    Off-ramp summary — Quyen casefile:

    • Quyen off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Quyen 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 Quyen — the packet meets the off-ramp’s published compliance standard.
    • When the Quyen 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. Triage on Quyen — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on Quyen — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on Quyen — off-ramp endpoint matched to a named exchange counterparty.
    4. File the Quyen 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 Quyen — the Professor stays on the casefile until a documented next step exists.

    What we read in a Quyen casefile:

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

    Lines the Professor will not cross:

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

  • BrightFxTrading — Annotated by the Professor

    // FROM THE CASEFILE — BRIGHTFXTRADING

    Funds you sent to BrightFxTrading (brightfxtrading.online) 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:

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

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

    • BrightFxTrading’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 BrightFxTrading off-ramp wallet against historical laundering throughput.
    • The BrightFxTrading packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for BrightFxTrading, 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. Casefile triage on BrightFxTrading — the submission is read; a written assessment is delivered.
    2. Forensic trace on BrightFxTrading — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the BrightFxTrading endpoint is named.
    4. Recovery filing on BrightFxTrading — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of BrightFxTrading — the Professor follows the casefile until next-step documentation exists.

    What the on-chain reading covers:

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

    What the Professor will never do — by policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace