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

Category: Scam Brokers

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

  • Professor’s Brief: Swiss win

    // FROM THE CASEFILE — SWISS WIN

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

    Trace summary — funds that left swiss-win.com:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Swiss win.
    • 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 Professor’s off-ramp note:

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

    The Professor’s recovery note for Swiss win:

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

    What the on-chain reading covers:

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

    Boundaries on every Swiss win casefile — never crossed:

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

    // FROM THE CASEFILE — AEX TRADE

    AEX Trade is a casefile under reading. The deposits to aextrade.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 aextrade.com:

    • Initial deposit hashes to the AEX Trade receiving address at aextrade.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 AEX Trade:

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

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

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

    Reading-list — chains and exchanges in scope:

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

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

    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

  • Reading the Chain: DMA Capitals

    // FROM THE CASEFILE — DMA CAPITALS

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

    Wallet trace — what the Professor maps:

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

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

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

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

    What the casefile records — chains and counterparties:

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

    Boundaries on every DMA Capitals casefile — never crossed:

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

  • Casefile AvaCapitalTrade — The Professor’s Note

    // FROM THE CASEFILE — AVACAPITALTRADE

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

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

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

    How a AvaCapitalTrade casefile becomes a regulator-ready filing:

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

    Chains and off-ramps the Professor follows:

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

    What the Professor will never do — by policy:

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

    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

  • Casefile Tellidex — The Professor’s Note

    // FROM THE CASEFILE — TELLIDEX

    Funds you sent to Tellidex (tellidex.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 tellidex.com:

    • Initial deposit hashes to the Tellidex receiving address at tellidex.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 map — where the funds left the chain:

    • Endpoint counterparty in the Tellidex casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Tellidex’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 Tellidex packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Tellidex 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. Casefile review on Tellidex — reading the submission against the no-go list.
    2. Trace mapping on Tellidex — pathway documented to chain-of-custody standard.
    3. Off-ramp naming on Tellidex — exchange endpoint identified.
    4. Packet filing on Tellidex — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
    5. Documented follow-through on Tellidex.

    Chains and off-ramps the Professor follows:

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

    Lines we never cross — by published policy:

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

  • Office Hours on Royale Team invesment

    // FROM THE CASEFILE — ROYALE TEAM INVESMENT

    When deposits to Royale Team invesment via royaleteaminfo.blogspot.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 royaleteaminfo.blogspot.com:

    • Deposit transaction hashes from the claimant wallet to the Royale Team invesment 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:

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

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

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

    What the casefile records — chains and counterparties:

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

    What is never asked of a claimant:

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

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

    // FROM THE CASEFILE — BIT LORDS

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

    Wallet trace — what the Professor maps:

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

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

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

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

    Chains and off-ramps the Professor follows:

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

    Lines we never cross — by published policy:

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

  • Office Hours on STARLIGHTCAPITAL.IO

    // FROM THE CASEFILE — STARLIGHTCAPITAL.IO

    The Professor opens the file on STARLIGHTCAPITAL.IO 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.

    Wallet trace — what the Professor maps:

    • Deposit confirmations from the claimant to STARLIGHTCAPITAL.IO’s receiving wallet at starlightcapital.io.
    • 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:

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

    How a STARLIGHTCAPITAL.IO casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    Boundaries on every STARLIGHTCAPITAL.IO casefile — never crossed:

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

    // FROM THE CASEFILE — METRO FXTRADING

    Metro Fxtrading is a casefile under reading. The deposits to metrofxtrading.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 metrofxtrading.com:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Metro Fxtrading.
    • 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 map — where the funds left the chain:

    • Off-ramp endpoint for Metro Fxtrading resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Metro Fxtrading’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Metro Fxtrading is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Metro Fxtrading 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 review on Metro Fxtrading — reading the submission against the no-go list.
    2. Trace mapping on Metro Fxtrading — pathway documented to chain-of-custody standard.
    3. Off-ramp naming on Metro Fxtrading — exchange endpoint identified.
    4. Packet filing on Metro Fxtrading — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
    5. Documented follow-through on Metro Fxtrading.

    What the Professor tracks across Metro Fxtrading casefiles:

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

    What is never asked of a claimant:

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

    Open a free consultation

    Bring the casefile to office hours — open a free consultation at /contact-us/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile GEINVGP — The Professor’s Note

    // FROM THE CASEFILE — GEINVGP

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

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

    The annotation continues — off-ramp endpoint:

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

    The Professor’s recovery note for GEINVGP:

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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