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

Tag: Investigbot

  • Investigbot — Annotated by the Professor

    // FROM THE CASEFILE — INVESTIGBOT

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

    • Initial deposit hashes to the Investigbot receiving address at investigbot.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 Investigbot casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Investigbot’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 Investigbot packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Investigbot 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. Read the Investigbot submission — written go/no-go returned.
    2. Map the Investigbot wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the Investigbot off-ramp — endpoint counterparty identified.
    4. Build and file the Investigbot recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the Investigbot file — until written next steps exist.

    What the Professor tracks across Investigbot casefiles:

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

    Lines we never cross — by published policy:

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