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

Category: Scam Brokers

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

  • Reading the Chain: prénom.nom@block-bridge.support

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to prénom.nom@block-bridge.support via prénom.nom@block-bridge.support 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 prénom.nom@block-bridge.support:

    • Claimant-to-platform deposit transactions on the deposit chain used by prénom.nom@block-bridge.support.
    • 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 prénom.nom@block-bridge.support:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

    • Chains tracked on prénom.nom@block-bridge.support — 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 prénom.nom@block-bridge.support — named exchange counterparties with public compliance contacts.
    • Filings supported on prénom.nom@block-bridge.support — 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 prénom.nom@block-bridge.support casefile — never request a seed phrase. Ever.
    • On the prénom.nom@block-bridge.support casefile — never request remote-access logins to a wallet or exchange.
    • On the prénom.nom@block-bridge.support casefile — never demand an upfront cash retainer to scope the matter.
    • On the prénom.nom@block-bridge.support casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the prénom.nom@block-bridge.support 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

    prénom.nom@block-bridge.support has been flagged as a fake broker/platform by IOSCO I-SCAN (France – Autorité des marchés financiers). reported 2025-11-14. 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/

  • Office Hours on WWCOIN

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to WWCOIN 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.

    Trace summary — funds that left this platform:

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

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    WWCOIN has been flagged as a fake broker/platform by IOSCO I-SCAN (New Zealand – Financial Markets Authority). reported 2025-08-18. Jurisdiction: New Zealand. 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/

  • From the Lectern: Clone Skyline Pro

    // FROM THE CASEFILE — CLONE SKYLINE PRO

    When deposits to Clone Skyline Pro via skylinepro.co 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 Clone Skyline Pro receiving address at skylinepro.co.
    • 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 Professor’s off-ramp note:

    • Clone Skyline Pro off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Clone Skyline Pro 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 Clone Skyline Pro — the packet meets the off-ramp’s published compliance standard.
    • When the Clone Skyline Pro 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. Read the Clone Skyline Pro submission — written go/no-go returned.
    2. Map the Clone Skyline Pro wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the Clone Skyline Pro off-ramp — endpoint counterparty identified.
    4. Build and file the Clone Skyline Pro recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the Clone Skyline Pro file — until written next steps exist.

    What the on-chain reading covers:

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

    Lines the Professor will not cross:

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

  • Office Hours on Merkanda Markets

    // FROM THE CASEFILE — MERKANDA MARKETS

    When deposits to Merkanda Markets via merkandamarkets.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 Merkanda Markets:

    • Deposit transaction hashes from the claimant wallet to the Merkanda Markets 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 annotation continues — off-ramp endpoint:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Recovery scammers do these things; the Professor never does:

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

    // FROM THE CASEFILE — LEISERTRADE

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

    Reading the wallets — Leisertrade casefile:

    • Initial deposit hashes to the Leisertrade receiving address at leisertrade.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 Leisertrade:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the casefile records — chains and counterparties:

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

    What the Professor will never do — by policy:

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

    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

  • From the Lectern: Atlas Trade Finance

    // FROM THE CASEFILE — ATLAS TRADE FINANCE

    When deposits to Atlas Trade Finance via atlas-finance.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.

    Wallet trace — what the Professor maps:

    • Deposit transaction hashes from the claimant wallet to the Atlas Trade Finance 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.

    From the lectern — off-ramp identification:

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

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

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

    Reading-list — chains and exchanges in scope:

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

    Boundaries on every Atlas Trade Finance casefile — never crossed:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: Bithebank

    // FROM THE CASEFILE — BITHEBANK

    When deposits to Bithebank via bithebank.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.

    From the marginalia — the deposit pathway:

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

    The Professor’s off-ramp note:

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

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

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

    What we read in a Bithebank casefile:

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

    • Bithebank policy — seed phrases are never requested.
    • Bithebank policy — remote-access logins are never requested.
    • Bithebank policy — no upfront cash retainer to scope.
    • Bithebank policy — no guaranteed-recovery language. None.
    • Bithebank 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 Clone Victorian Money Limited

    // FROM THE CASEFILE — CLONE VICTORIAN MONEY LIMITED

    Clone Victorian Money Limited is a casefile under reading. The deposits to victorian-fx.pro 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 — Clone Victorian Money Limited casefile:

    • Deposit confirmations from the claimant to Clone Victorian Money Limited’s receiving wallet at victorian-fx.pro.
    • 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:

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

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

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

    Chains and off-ramps the Professor follows:

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

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

  • Tether Earn Mining — Annotated by the Professor

    // FROM THE CASEFILE — TETHER EARN MINING

    Tether Earn Mining is a casefile under reading. The deposits to tetherearnmining.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 tetherearnmining.com:

    • Deposit confirmations from the claimant to Tether Earn Mining’s receiving wallet at tetherearnmining.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:

    • Endpoint counterparty in the Tether Earn Mining casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Tether Earn Mining’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 Tether Earn Mining packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Tether Earn Mining 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. Triage on Tether Earn Mining — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on Tether Earn Mining — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on Tether Earn Mining — off-ramp endpoint matched to a named exchange counterparty.
    4. File the Tether Earn Mining 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 Tether Earn Mining — the Professor stays on the casefile until a documented next step exists.

    What the casefile records — chains and counterparties:

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

    Lines we never cross — by published policy:

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

  • Office Hours on INTLBTC

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to INTLBTC via intlbtc.es 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 intlbtc.es:

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

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    INTLBTC has been flagged as a fake broker/platform by IOSCO I-SCAN (Spain – Comisión Nacional del Mercado de Valores). reported 2026-02-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/