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

Tag: FxOnUs

  • Casefile FxOnUs — The Professor’s Note

    // FROM THE CASEFILE — FXONUS

    FxOnUs, operating from fxonus.com, 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 fxonus.com:

    • Initial deposit hashes to the FxOnUs receiving address at fxonus.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.

    Off-ramp reading — exchange counterparty for FxOnUs:

    • FxOnUs off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The FxOnUs 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 FxOnUs — the packet meets the off-ramp’s published compliance standard.
    • When the FxOnUs 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 FxOnUs submission — written go/no-go returned.
    2. Map the FxOnUs wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the FxOnUs off-ramp — endpoint counterparty identified.
    4. Build and file the FxOnUs recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the FxOnUs file — until written next steps exist.

    Reading-list — chains and exchanges in scope:

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

    Boundaries on every FxOnUs casefile — never crossed:

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