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

Category: Scam Brokers

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

  • From the Lectern: Trado Banco

    // FROM THE CASEFILE — TRADO BANCO

    The Professor opens the file on Trado Banco 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.

    On-chain reading — wallet flow for Trado Banco:

    • Claimant-to-platform deposit transactions on the deposit chain used by Trado Banco.
    • 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 summary — Trado Banco casefile:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    What is never asked of a claimant:

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

    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

  • Professor’s Brief: Celestial Trader

    // FROM THE CASEFILE — CELESTIAL TRADER

    Celestial Trader, operating from celestialtrader.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 Celestial Trader:

    • Claimant-to-platform deposit transactions on the deposit chain used by Celestial Trader.
    • 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 Celestial Trader resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Celestial Trader’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Celestial Trader is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Celestial Trader 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. First read on Celestial Trader — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on Celestial Trader — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for Celestial Trader is named to a centralised exchange wallet.
    4. Packet filing on Celestial Trader — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with Celestial Trader until a documented outcome or escalation step is on file.

    What the casefile records — chains and counterparties:

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

    What is never asked of a claimant:

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

    // FROM THE CASEFILE — INVESTJPM

    Funds you sent to InvestJPM (investjpm.org) 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.

    On-chain reading — wallet flow for InvestJPM:

    • Claimant-to-platform deposit transactions on the deposit chain used by InvestJPM.
    • 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 summary — InvestJPM casefile:

    • Off-ramp endpoint for InvestJPM resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • InvestJPM’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for InvestJPM is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the InvestJPM 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 InvestJPM — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on InvestJPM — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for InvestJPM is named to a centralised exchange wallet.
    4. Packet filing on InvestJPM — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with InvestJPM until a documented outcome or escalation step is on file.

    What the on-chain reading covers:

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

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

    // FROM THE CASEFILE — WEXNOPRO

    When deposits to Wexnopro via wexnopro.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 — Wexnopro casefile:

    • Initial deposit hashes to the Wexnopro receiving address at wexnopro.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 Professor’s off-ramp note:

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

    How a Wexnopro casefile becomes a regulator-ready filing:

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

    Chains and off-ramps the Professor follows:

    • Chains the Professor reads for Wexnopro casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
    • Off-ramps named in Wexnopro — major centralised venues with compliance desks that accept regulator-grade packets.
    • Filing pathways available on Wexnopro — 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 Wexnopro — no seed-phrase requests, period.
    • Hard line on Wexnopro — no remote logins requested.
    • Hard line on Wexnopro — no upfront cash retainer.
    • Hard line on Wexnopro — no guarantee language.
    • Hard line on Wexnopro — no unsolicited phone outreach.

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile BETTAMENT MARKET — The Professor’s Note

    // FROM THE CASEFILE — BETTAMENT MARKET

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

    On-chain reading — wallet flow for BETTAMENT MARKET:

    • Initial deposit hashes to the BETTAMENT MARKET receiving address at bettamentmarket-pro.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 Professor’s off-ramp note:

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

    The Professor’s recovery note for BETTAMENT MARKET:

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

    What the casefile records — chains and counterparties:

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

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile UNISON — The Professor’s Note

    // FROM THE CASEFILE — UNISON

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

    The annotation reads — wallet trace:

    • Deposit confirmations from the claimant to UNISON’s receiving wallet at unison-corporation.com.
    • Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
    • Cross-chain bridge transactions where the operator routed value out of the deposit chain.
    • Mixer or coin-join interactions, where applicable.
    • Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

    Off-ramp reading — exchange counterparty for UNISON:

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

    The Professor’s recovery note for UNISON:

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

    Reading-list — chains and exchanges in scope:

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

    Lines the Professor will not cross:

    • UNISON policy — seed phrases are never requested.
    • UNISON policy — remote-access logins are never requested.
    • UNISON policy — no upfront cash retainer to scope.
    • UNISON policy — no guaranteed-recovery language. None.
    • UNISON policy — no unsolicited calls. The Professor responds in writing only.

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: TradeGlobFx

    // FROM THE CASEFILE — TRADEGLOBFX

    The Professor opens the file on TradeGlobFx the same way every casefile is opened — by treating the wallet history as text and the off-ramp endpoint as the citation a regulator can verify.

    From the marginalia — the deposit pathway:

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

    • Off-ramp endpoint for TradeGlobFx resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • TradeGlobFx’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for TradeGlobFx is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the TradeGlobFx 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. Casefile triage on TradeGlobFx — the submission is read; a written assessment is delivered.
    2. Forensic trace on TradeGlobFx — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the TradeGlobFx endpoint is named.
    4. Recovery filing on TradeGlobFx — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of TradeGlobFx — the Professor follows the casefile until next-step documentation exists.

    What we read in a TradeGlobFx casefile:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: PipsForex

    // FROM THE CASEFILE — PIPSFOREX

    PipsForex is a casefile under reading. The deposits to pipsforex.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 — PipsForex casefile:

    • Claimant-to-platform deposit transactions on the deposit chain used by PipsForex.
    • 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 summary — PipsForex casefile:

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

    How a PipsForex casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

    • Chains the Professor reads for PipsForex casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
    • Off-ramps named in PipsForex — major centralised venues with compliance desks that accept regulator-grade packets.
    • Filing pathways available on PipsForex — 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:

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

    // FROM THE CASEFILE — WEFI

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

    The annotation reads — wallet trace:

    • Deposit-side hashes from claimant wallets into WeFi’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:

    • WeFi off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The WeFi 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 WeFi — the packet meets the off-ramp’s published compliance standard.
    • When the WeFi 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 — WeFi casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — WeFi deposit and forwarding wallets captured.
    3. Endpoint identification — WeFi off-ramp wallet named.
    4. Filing — WeFi packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — WeFi stays on file until a documented next step is reached.

    What the casefile records — chains and counterparties:

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

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

    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

  • Reading the Chain: Moon Chart Signals

    // FROM THE CASEFILE — MOON CHART SIGNALS

    Moon Chart Signals is a casefile under reading. The deposits to moonchartsignals.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 Moon Chart Signals:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    Chains and off-ramps the Professor follows:

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

    Lines the Professor will not cross:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace