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: get stolen crypto back

  • Casefile NavionFX — The Professor’s Note

    // FROM THE CASEFILE — NAVIONFX

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

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

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

    How a NavionFX casefile becomes a regulator-ready filing:

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

    What the casefile records — chains and counterparties:

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

    Boundaries on every NavionFX casefile — never crossed:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: Capital FX

    // FROM THE CASEFILE — CAPITAL FX

    Capital FX is a casefile under reading. The deposits to capitalfxweb.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 Capital FX:

    • Initial deposit hashes to the Capital FX receiving address at capitalfxweb.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.

    From the lectern — off-ramp identification:

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

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

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

    Chains and off-ramps the Professor follows:

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

    Lines we never cross — by published policy:

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

  • From the Lectern: Capital FM

    // FROM THE CASEFILE — CAPITAL FM

    Capital FM, operating from capitalfm.cc, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    On-chain reading — wallet flow for Capital FM:

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

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

    How a Capital FM casefile becomes a regulator-ready filing:

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

    What the casefile records — chains and counterparties:

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

    Boundaries on every Capital FM casefile — never crossed:

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