Protect your case: initiate contact through cryptocurrencyprofessor.com. Never share your seed phrase.

Category: Scam Brokers

Annotated readings of brokers and platforms the Cryptocurrency Professor has documented.

  • Office Hours on info@nls.airliquide.com

    FROM THE CASEFILE, CTK NETWORK

    When deposits to info@nls.airliquide.com via info@nls.airliquide.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 info@nls.airliquide.com:

    • Deposit confirmations from the claimant to info@nls.airliquide.com’s receiving wallet at info@nls.airliquide.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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross, by published policy:

    • info@nls.airliquide.com policy, seed phrases are never requested.
    • info@nls.airliquide.com policy, remote-access logins are never requested.
    • info@nls.airliquide.com policy, no upfront cash retainer to scope.
    • info@nls.airliquide.com policy, no guaranteed-recovery language. None.
    • info@nls.airliquide.com 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

    info@nls.airliquide.com has been flagged as a fake broker/platform by IOSCO I-SCAN (France – Autorité des marchés financiers). reported 2024-02-21. Jurisdiction: France. 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/

  • Professor’s Brief: Gold E

    FROM THE CASEFILE, GOLD E

    When a deposit ledgered to Gold E at gold-e.cn stops responding, the trail does not stop with the silence, the on-chain record is the syllabus, and the Professor reads it carefully.

    From the marginalia, the deposit pathway:

    • Initial deposit hashes to the Gold E receiving address at gold-e.cn.
    • 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 map, where the funds left the chain:

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

    How a Gold E casefile becomes a evidence filing:

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

    What the on-chain reading covers:

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

    Lines we never cross, by published policy:

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

  • Office Hours on ForexTD

    FROM THE CASEFILE, FOREXTD

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

    On-chain reading, wallet flow for ForexTD:

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

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

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

    What the on-chain reading covers:

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

    Lines the Professor will not cross:

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

  • Office Hours on icbc-gb.com (Clone of FCA authorised firm)

    FROM THE CASEFILE, CTK NETWORK

    When deposits to icbc-gb.com (Clone of FCA authorised firm) via icbc-gb.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 icbc-gb.com:

    • Deposit confirmations from the claimant to icbc-gb.com (Clone of FCA authorised firm)’s receiving wallet at icbc-gb.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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross, by published policy:

    • icbc-gb.com (Clone of FCA authorised firm) policy, seed phrases are never requested.
    • icbc-gb.com (Clone of FCA authorised firm) policy, remote-access logins are never requested.
    • icbc-gb.com (Clone of FCA authorised firm) policy, no upfront cash retainer to scope.
    • icbc-gb.com (Clone of FCA authorised firm) policy, no guaranteed-recovery language. None.
    • icbc-gb.com (Clone of FCA authorised firm) 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

    icbc-gb.com (Clone of FCA authorised firm) has been flagged as a fake broker/platform by IOSCO I-SCAN (United Kingdom – Financial Conduct Authority). reported 2024-12-11. Jurisdiction: United Kingdom. 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/

  • Professor’s Brief: Livecapitaltrading

    FROM THE CASEFILE, LIVECAPITALTRADING

    Livecapitaltrading is a casefile under reading. The deposits to livecapitaltrading.click 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.

    Trace summary, funds that left livecapitaltrading.click:

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

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

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

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

    What we read in a Livecapitaltrading casefile:

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

    Lines we never cross, by published policy:

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

    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: TRADINGBROKER FX

    FROM THE CASEFILE, TRADINGBROKER FX

    When deposits to TRADINGBROKER FX via tradebrokerfx.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 TRADINGBROKER FX.
    • 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:

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

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

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

    What the Professor tracks across TRADINGBROKER FX casefiles:

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

    • What the Professor will not do on TRADINGBROKER FX, ask for a seed phrase.
    • What the Professor will not do on TRADINGBROKER FX, request remote-access logins.
    • What the Professor will not do on TRADINGBROKER FX, demand cash up front.
    • What the Professor will not do on TRADINGBROKER FX, promise a guarantee.
    • What the Professor will not do on TRADINGBROKER FX, 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 BTCC Lithuania Limited, UAB BTCC, The Professor’s Note

    FROM THE CASEFILE, BERKAT FD SDN BHD

    The Professor opens the file on BTCC Lithuania Limited, UAB BTCC 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:

    • Claimant-to-platform deposit transactions on the deposit chain used by BTCC Lithuania Limited, UAB BTCC.
    • 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:

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

    How a BTCC Lithuania Limited, UAB BTCC casefile becomes a evidence filing:

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

    Reading-list, chains and exchanges in scope:

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

    What is never asked of a claimant:

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

    Why this platform is on our casefile

    BTCC Lithuania Limited, UAB BTCC has been flagged as a fake broker/platform by IOSCO I-SCAN (Quebec – Autorité des marchés financiers). reported 2025-11-28. Jurisdiction: Quebec. 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 RoxCapitals

    FROM THE CASEFILE, ROXCAPITALS

    Funds you sent to RoxCapitals (roxcapitals.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.

    Trace summary, funds that left roxcapitals.com:

    • Deposit confirmations from the claimant to RoxCapitals’s receiving wallet at roxcapitals.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 annotation continues, off-ramp endpoint:

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

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

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

    What the Professor tracks across RoxCapitals casefiles:

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

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

  • Casefile Capitalinfusions, The Professor’s Note

    FROM THE CASEFILE, CAPITALINFUSIONS

    Capitalinfusions is a casefile under reading. The deposits to capital-infusions.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.

    Trace summary, funds that left capital-infusions.com:

    • Initial deposit hashes to the Capitalinfusions receiving address at capital-infusions.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 reading, exchange counterparty for Capitalinfusions:

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

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

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

    What the casefile records, chains and counterparties:

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

    What is never asked of a claimant:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: Urbisfx

    FROM THE CASEFILE, WORLD MARKETS

    When deposits to Urbisfx via urbisfx.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.

    On-chain reading, wallet flow for Urbisfx:

    • Claimant-to-platform deposit transactions on the deposit chain used by Urbisfx.
    • 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 reading, exchange counterparty for Urbisfx:

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

    Recovery pathway, how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

    Why this platform is on our casefile

    Urbisfx has been flagged as a fake broker/platform by IOSCO I-SCAN (Spain – Comisión Nacional del Mercado de Valores). reported 2023-07-10. Jurisdiction: Spain. 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/