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

Tag: scam broker

  • TOPMETROFX — Annotated by the Professor

    // FROM THE CASEFILE — TOPMETROFX

    The Professor opens the file on TOPMETROFX 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 TOPMETROFX:

    • Deposit confirmations from the claimant to TOPMETROFX’s receiving wallet at topmetrofx.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 Professor’s off-ramp note:

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

    The Professor’s recovery note for TOPMETROFX:

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

    What we read in a TOPMETROFX casefile:

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

    Lines we never cross — by published policy:

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

  • Blue Ocean Voyages — Annotated by the Professor

    // FROM THE CASEFILE — BLUE OCEAN VOYAGES

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

    The annotation reads — wallet trace:

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

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

    How a Blue Ocean Voyages casefile becomes a regulator-ready filing:

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Bancfx

    // FROM THE CASEFILE — BANCFX

    When deposits to Bancfx via 46.166.173.124 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:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Lines the Professor will not cross:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: UOSHING

    // FROM THE CASEFILE — UOSHING

    The Professor opens the file on UOSHING 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 UOSHING:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for UOSHING.
    • Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
    • Bridge events into chains where the operator can off-ramp at scale.
    • Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
    • Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

    Off-ramp reading — exchange counterparty for UOSHING:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the casefile records — chains and counterparties:

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

    What is never asked of a claimant:

    • Boundary on UOSHING — seed phrases are off-limits.
    • Boundary on UOSHING — remote logins are off-limits.
    • Boundary on UOSHING — upfront cash retainers are off-limits.
    • Boundary on UOSHING — guaranteed-recovery promises are off-limits.
    • Boundary on UOSHING — 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

  • Ultimate Wealth Solutions — Annotated by the Professor

    // FROM THE CASEFILE — ULTIMATE WEALTH SOLUTIONS

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

    Wallet trace — what the Professor maps:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Ultimate Wealth Solutions.
    • 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:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the casefile records — chains and counterparties:

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

    Lines we never cross — by published policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Professor’s Brief: Mexsus Limited

    // FROM THE CASEFILE — MEXSUS LIMITED

    Mexsus Limited is a casefile under reading. The deposits to zfinances.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 confirmations from the claimant to Mexsus Limited’s receiving wallet at zfinances.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 map — where the funds left the chain:

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

    How a Mexsus Limited casefile becomes a regulator-ready filing:

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

    What we read in a Mexsus Limited casefile:

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

    What is never asked of a claimant:

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

  • Casefile Mega Menara Mas Berjangka — The Professor’s Note

    // FROM THE CASEFILE — MEGA MENARA MAS BERJANGKA

    Mega Menara Mas Berjangka is a casefile under reading. The deposits to megamenaramas.co.id 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 — Mega Menara Mas Berjangka casefile:

    • Deposit transaction hashes from the claimant wallet to the Mega Menara Mas Berjangka 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 Mega Menara Mas Berjangka:

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

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

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

    What the on-chain reading covers:

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

    Recovery scammers do these things; the Professor never does:

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

  • Office Hours on TradeBaionics

    // FROM THE CASEFILE — TRADEBAIONICS

    TradeBaionics, operating from tradebaionics.io, 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 tradebaionics.io:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    Reading-list — chains and exchanges in scope:

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

    What is never asked of a claimant:

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

  • Professor’s Brief: AR Forex

    // FROM THE CASEFILE — AR FOREX

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

    Trace summary — funds that left ar-forex.com:

    • Deposit confirmations from the claimant to AR Forex’s receiving wallet at ar-forex.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 Professor’s off-ramp note:

    • AR Forex’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 AR Forex off-ramp wallet against historical laundering throughput.
    • The AR Forex packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for AR Forex, 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. Read the AR Forex submission — written go/no-go returned.
    2. Map the AR Forex wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the AR Forex off-ramp — endpoint counterparty identified.
    4. Build and file the AR Forex recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the AR Forex file — until written next steps exist.

    Reading-list — chains and exchanges in scope:

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

    Recovery scammers do these things; the Professor never does:

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

  • Reading the Chain: ST5

    // FROM THE CASEFILE — ST5

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

    From the marginalia — the deposit pathway:

    • Initial deposit hashes to the ST5 receiving address at app.st5s.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:

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

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

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

    Reading-list — chains and exchanges in scope:

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

    What is never asked of a claimant:

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