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

Tag: crypto scam recovery

  • Casefile SilverX Markets — The Professor’s Note

    // FROM THE CASEFILE — SILVERX MARKETS

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

    From the marginalia — the deposit pathway:

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

    Off-ramp summary — SilverX Markets casefile:

    • On the SilverX Markets casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
    • The off-ramp wallet for SilverX Markets is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the SilverX Markets casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, SilverX Markets escalates to IC3, state AG, and civil-discovery overlay.

    The Professor’s recovery note for SilverX Markets:

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

    What the Professor tracks across SilverX Markets casefiles:

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

    Boundaries on every SilverX Markets casefile — never crossed:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Swiss Capital Hub — Annotated by the Professor

    // FROM THE CASEFILE — SWISS CAPITAL HUB

    Funds you sent to Swiss Capital Hub (swisscapitalhub.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 Swiss Capital Hub:

    • Deposit confirmations from the claimant to Swiss Capital Hub’s receiving wallet at swisscapitalhub.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.

    From the lectern — off-ramp identification:

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

    How a Swiss Capital Hub casefile becomes a regulator-ready filing:

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

    What the Professor tracks across Swiss Capital Hub casefiles:

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

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

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

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

    Wallet trace — what the Professor maps:

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

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

    How a SkywardAsset casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

    • Chains in scope for SkywardAsset — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
    • Off-ramps in scope for SkywardAsset — named centralised exchanges with compliance leverage.
    • Filings supported on SkywardAsset — 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 SkywardAsset — ask for a seed phrase.
    • What the Professor will not do on SkywardAsset — request remote-access logins.
    • What the Professor will not do on SkywardAsset — demand cash up front.
    • What the Professor will not do on SkywardAsset — promise a guarantee.
    • What the Professor will not do on SkywardAsset — 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

    Why this platform is on our casefile

    SkywardAsset has been flagged as a fake broker/platform by IOSCO I-SCAN (Malaysia – Securities Commission). reported 2024-05-07. Jurisdiction: Malaysia. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.iosco.org/i-scan/

  • Reading the Chain: Edgcreinv

    // FROM THE CASEFILE — WORLD MARKETS

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

    On-chain reading — wallet flow for Edgcreinv:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

    Why this platform is on our casefile

    Edgcreinv has been flagged as a fake broker/platform by IOSCO I-SCAN (Luxembourg – Commission de Surveillance du Secteur Financier). reported 2025-02-19. Jurisdiction: Luxembourg. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.iosco.org/i-scan/

  • From the Lectern: Oubo Global

    // FROM THE CASEFILE — OUBO GLOBAL

    Oubo Global is a casefile under reading. The deposits to oubowfx.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 Oubo Global:

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

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

    How a Oubo Global casefile becomes a regulator-ready filing:

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

    What the Professor tracks across Oubo Global casefiles:

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

    Boundaries on every Oubo Global casefile — never crossed:

    • Oubo Global policy — seed phrases are never requested.
    • Oubo Global policy — remote-access logins are never requested.
    • Oubo Global policy — no upfront cash retainer to scope.
    • Oubo Global policy — no guaranteed-recovery language. None.
    • Oubo Global policy — no unsolicited calls. The Professor responds in writing 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

  • Office Hours on G7 Brics

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

    When deposits to G7 Brics via g7-brics.site go quiet, the on-chain record stays loud. The Professor’s reading begins where the platform’s silence does — with the wallet that received the funds and the path it took afterward.

    Wallet trace — what the Professor maps:

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

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

    How a G7 Brics casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

    • Chains in scope for G7 Brics — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
    • Off-ramps in scope for G7 Brics — named centralised exchanges with compliance leverage.
    • Filings supported on G7 Brics — 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 G7 Brics — ask for a seed phrase.
    • What the Professor will not do on G7 Brics — request remote-access logins.
    • What the Professor will not do on G7 Brics — demand cash up front.
    • What the Professor will not do on G7 Brics — promise a guarantee.
    • What the Professor will not do on G7 Brics — 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

    Why this platform is on our casefile

    G7 Brics has been flagged as a fake broker/platform by IOSCO I-SCAN (United Kingdom – Financial Conduct Authority). reported 2025-07-10. Jurisdiction: United Kingdom. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.iosco.org/i-scan/

  • Casefile LumineTrade — The Professor’s Note

    // FROM THE CASEFILE — LUMINETRADE

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

    Trace summary — funds that left lumine-trd.com:

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

    • LumineTrade’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 LumineTrade off-ramp wallet against historical laundering throughput.
    • The LumineTrade packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for LumineTrade, 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 LumineTrade — the submission is read; a written assessment is delivered.
    2. Forensic trace on LumineTrade — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the LumineTrade endpoint is named.
    4. Recovery filing on LumineTrade — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of LumineTrade — the Professor follows the casefile until next-step documentation exists.

    Chains and off-ramps the Professor follows:

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

    What the Professor will never do — by policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Nex Bridge FX — The Professor’s Note

    // FROM THE CASEFILE — NEX BRIDGE FX

    Nex Bridge FX is a casefile under reading. The deposits to nexbridgefx.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 Nex Bridge FX:

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

    Off-ramp map — where the funds left the chain:

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

    How a Nex Bridge FX casefile becomes a regulator-ready filing:

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

    What we read in a Nex Bridge FX casefile:

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

    Lines the Professor will not cross:

    • Nex Bridge FX policy — seed phrases are never requested.
    • Nex Bridge FX policy — remote-access logins are never requested.
    • Nex Bridge FX policy — no upfront cash retainer to scope.
    • Nex Bridge FX policy — no guaranteed-recovery language. None.
    • Nex Bridge FX policy — no unsolicited calls. The Professor responds in writing 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

  • From the Lectern: Boney Market

    // FROM THE CASEFILE — BONEY MARKET

    When deposits to Boney Market via boneymarket.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:

    • Deposit-side hashes from claimant wallets into Boney Market’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.

    The Professor’s off-ramp note:

    • Boney 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 Boney 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 Boney Market — the packet meets the off-ramp’s published compliance standard.
    • When the Boney Market 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 — Boney Market casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — Boney Market deposit and forwarding wallets captured.
    3. Endpoint identification — Boney Market off-ramp wallet named.
    4. Filing — Boney Market packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — Boney Market stays on file until a documented next step is reached.

    What the Professor tracks across Boney Market casefiles:

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

    Lines the Professor will not cross:

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

  • Office Hours on OTC Markets

    // FROM THE CASEFILE — OTC MARKETS

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

    From the marginalia — the deposit pathway:

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

    Off-ramp reading — exchange counterparty for OTC Markets:

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

    How a OTC Markets casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    Lines the Professor will not cross:

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