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 prénom.nom@polegestiondeblock.com

    FROM THE CASEFILE, CTK NETWORK

    When deposits to prénom.nom@polegestiondeblock.com via prénom.nom@polegestiondeblock.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 prénom.nom@polegestiondeblock.com:

    • Deposit confirmations from the claimant to prénom.nom@polegestiondeblock.com’s receiving wallet at prénom.nom@polegestiondeblock.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:

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

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

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

    What the on-chain reading covers:

    • Deposit-side chains in prénom.nom@polegestiondeblock.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 prénom.nom@polegestiondeblock.com packets, centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on prénom.nom@polegestiondeblock.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:

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

    prénom.nom@polegestiondeblock.com has been flagged as a fake broker/platform by IOSCO I-SCAN (France – Autorité des marchés financiers). reported 2026-07-07. 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/

  • Casefile Phemex, The Professor’s Note

    FROM THE CASEFILE, PHEMEX

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

    Reading the wallets, Phemex casefile:

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

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

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

    Recovery pathway, how this casefile moves toward filing:

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

    What the Professor tracks across Phemex casefiles:

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

    What is never asked of a claimant:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile American FX, The Professor’s Note

    FROM THE CASEFILE, AMERICAN FX

    Funds you sent to American FX (americanfxtrading.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.

    Trace summary, funds that left americanfxtrading.us:

    • Deposit transaction hashes from the claimant wallet to the American FX 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, American FX casefile:

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

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

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

    What we read in a American FX casefile:

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

    What the Professor will never do, by policy:

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

  • Office Hours on Market Giants

    FROM THE CASEFILE, MARKET GIANTS

    Market Giants is a casefile under reading. The deposits to marketgiants.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.

    Reading the wallets, Market Giants casefile:

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

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

    How a Market Giants casefile becomes a evidence filing:

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

    Reading-list, chains and exchanges in scope:

    • Chains tracked on Market Giants, 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 Market Giants, named exchange counterparties with public compliance contacts.
    • Filings supported on Market Giants, 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 Market Giants, ask for a seed phrase.
    • What the Professor will not do on Market Giants, request remote-access logins.
    • What the Professor will not do on Market Giants, demand cash up front.
    • What the Professor will not do on Market Giants, promise a guarantee.
    • What the Professor will not do on Market Giants, 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

  • Office Hours on INTERNATIONAL BASIC SOUL SL (MADRID)

    FROM THE CASEFILE, BTCUSDT INVESTMENT

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

    The Professor’s off-ramp note:

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

    How a INTERNATIONAL BASIC SOUL SL (MADRID) casefile becomes a evidence filing:

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

    Reading-list, chains and exchanges in scope:

    • Chains in scope for INTERNATIONAL BASIC SOUL SL (MADRID), the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
    • Off-ramps in scope for INTERNATIONAL BASIC SOUL SL (MADRID), named centralised exchanges with compliance leverage.
    • Filings supported on INTERNATIONAL BASIC SOUL SL (MADRID), 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 INTERNATIONAL BASIC SOUL SL (MADRID), ask for a seed phrase.
    • What the Professor will not do on INTERNATIONAL BASIC SOUL SL (MADRID), request remote-access logins.
    • What the Professor will not do on INTERNATIONAL BASIC SOUL SL (MADRID), demand cash up front.
    • What the Professor will not do on INTERNATIONAL BASIC SOUL SL (MADRID), promise a guarantee.
    • What the Professor will not do on INTERNATIONAL BASIC SOUL SL (MADRID), call you out of the blue.

    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

    INTERNATIONAL BASIC SOUL SL (MADRID) has been flagged as a fake broker/platform by IOSCO I-SCAN (Spain – Comisión Nacional del Mercado de Valores). reported 2021-05-04. 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/

  • Casefile Lloyds Capital, The Professor’s Note

    FROM THE CASEFILE, LLOYDS CAPITAL

    Funds you sent to Lloyds Capital (lloyds-capital.net) 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 lloyds-capital.net:

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

    The Professor’s off-ramp note:

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

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

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

    What the Professor tracks across Lloyds Capital casefiles:

    • Deposit-side chains in Lloyds Capital casefiles, typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT), with bridge crossings noted.
    • Off-ramps named in Lloyds Capital packets, centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Lloyds Capital, IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    Lines we never cross, by published policy:

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

  • Reading the Chain: Elcomercio IX

    FROM THE CASEFILE, ELCOMERCIO IX

    Elcomercio IX, operating from elcomercio-ix.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 Elcomercio IX:

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

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

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

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

    What the casefile records, chains and counterparties:

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

    What the Professor will never do, by policy:

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

  • Office Hours on PiexBit

    FROM THE CASEFILE, CTK NETWORK

    When deposits to PiexBit via piexbit.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 piexbit.com:

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

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross, by published policy:

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

    PiexBit has been flagged as a fake broker/platform by IOSCO I-SCAN (United Kingdom – Financial Conduct Authority). reported 2024-08-21. 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/

  • Casefile Apex Trade, The Professor’s Note

    FROM THE CASEFILE, APEX TRADE

    When a deposit ledgered to Apex Trade at apex-trade.capital stops responding, the trail does not stop with the silence, the on-chain record is the syllabus, and the Professor reads it carefully.

    The annotation reads, wallet trace:

    • Deposit-side hashes from claimant wallets into Apex Trade’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, Apex Trade casefile:

    • Endpoint counterparty in the Apex Trade casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Apex Trade’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 Apex Trade packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Apex Trade 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.

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

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

    What the casefile records, chains and counterparties:

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

    Lines we never cross, by published policy:

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

  • Professor’s Brief: AES

    FROM THE CASEFILE, AES

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

    The annotation reads, wallet trace:

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

    Off-ramp reading, exchange counterparty for AES:

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

    The Professor’s recovery note for AES:

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

    What the Professor tracks across AES casefiles:

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

    Lines the Professor will not cross:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace