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 →

Tag: get stolen crypto back

  • Casefile Amxer Markets — The Professor’s Note

    // FROM THE CASEFILE — AMXER MARKETS

    The Professor opens the file on Amxer Markets 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 amxermarkets.com:

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

    The annotation continues — off-ramp endpoint:

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

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

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

    What the casefile records — chains and counterparties:

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

    What is never asked of a claimant:

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

  • From the Lectern: Winex Markets

    // FROM THE CASEFILE — WINEX MARKETS

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

    Reading the wallets — Winex Markets casefile:

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

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

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

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

    Chains and off-ramps the Professor follows:

    • Chains the Winex Markets 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 Winex Markets — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the Winex Markets 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 the Professor will never do — by policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Fortuna Markets

    // FROM THE CASEFILE — FORTUNA MARKETS

    Fortuna Markets, operating from fortunamarkets.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 Fortuna Markets’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.

    From the lectern — off-ramp identification:

    • Endpoint counterparty in the Fortuna Markets casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Fortuna Markets’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 Fortuna Markets packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Fortuna Markets off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

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

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

    Chains and off-ramps the Professor follows:

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

    What the Professor will never do — by policy:

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

  • Zen Capital — Annotated by the Professor

    // FROM THE CASEFILE — ZEN CAPITAL

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

    The annotation reads — wallet trace:

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

    The annotation continues — off-ramp endpoint:

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

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

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

    Reading-list — chains and exchanges in scope:

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

    Lines we never cross — by published policy:

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

    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: USDETF

    // FROM THE CASEFILE — USDETF

    Funds you sent to USDETF (dappusdetf.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.

    From the marginalia — the deposit pathway:

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

    From the lectern — off-ramp identification:

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

    How a USDETF casefile becomes a regulator-ready filing:

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

    What the casefile records — chains and counterparties:

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

    // FROM THE CASEFILE — TRADEWISE (TRADEWISEFX)

    The Professor opens the file on Tradewise (TradewiseFX) 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:

    • Initial deposit hashes to the Tradewise (TradewiseFX) receiving address at tradewise-fx.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:

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

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

    What the on-chain reading covers:

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

    Boundaries on every Tradewise (TradewiseFX) casefile — never crossed:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: Social Trade Pro

    // FROM THE CASEFILE — SOCIAL TRADE PRO

    When deposits to Social Trade Pro via socialtradepro.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 — Social Trade Pro casefile:

    • Deposit confirmations from the claimant to Social Trade Pro’s receiving wallet at socialtradepro.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 Social Trade Pro:

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

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

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

    Chains and off-ramps the Professor follows:

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

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

    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 Clayton Markets

    // FROM THE CASEFILE — CLAYTON MARKETS

    Funds you sent to Clayton Markets (claytonmarkets.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.

    On-chain reading — wallet flow for Clayton Markets:

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

    From the lectern — off-ramp identification:

    • Clayton Markets off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Clayton Markets 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 Clayton Markets — the packet meets the off-ramp’s published compliance standard.
    • When the Clayton Markets 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 Clayton Markets:

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

    What the casefile records — chains and counterparties:

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

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

    // FROM THE CASEFILE — MERCADOSINVEST

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

    Wallet trace — what the Professor maps:

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

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

    How a MercadosInvest casefile becomes a regulator-ready filing:

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

    What the Professor tracks across MercadosInvest casefiles:

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

    Boundaries on every MercadosInvest casefile — never crossed:

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

  • Casefile Algorithm Global — The Professor’s Note

    // FROM THE CASEFILE — ALGORITHM GLOBAL

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

    • Initial deposit hashes to the Algorithm Global receiving address at algoglobalinternational.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:

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

    Reading-list — chains and exchanges in scope:

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

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace