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

Tag: report a scam

  • SwissDirekt — Annotated by the Professor

    // FROM THE CASEFILE — SWISSDIREKT

    Funds you sent to SwissDirekt (swissdirekt.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:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What we read in a SwissDirekt casefile:

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

    • Hard line on SwissDirekt — no seed-phrase requests, period.
    • Hard line on SwissDirekt — no remote logins requested.
    • Hard line on SwissDirekt — no upfront cash retainer.
    • Hard line on SwissDirekt — no guarantee language.
    • Hard line on SwissDirekt — 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

  • Professor’s Brief: FTMX Global

    // FROM THE CASEFILE — FTMX GLOBAL

    The Professor opens the file on FTMX 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 FTMX Global receiving address at ftmxglobal.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:

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

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

    What the casefile records — chains and counterparties:

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

    What the Professor will never do — by policy:

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

  • Office Hours on Superbinvest Group

    // FROM THE CASEFILE — SUPERBINVEST GROUP

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

    On-chain reading — wallet flow for Superbinvest Group:

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

    Off-ramp reading — exchange counterparty for Superbinvest Group:

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

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

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

    What the Professor tracks across Superbinvest Group casefiles:

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

    Lines the Professor will not cross:

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

    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

  • Office Hours on LECS Crypto

    // FROM THE CASEFILE — LECS CRYPTO

    When deposits to LECS Crypto via cryptolecs.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 LECS Crypto’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:

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

    How a LECS Crypto casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

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

    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

  • IMCTradingFX — Annotated by the Professor

    // FROM THE CASEFILE — IMCTRADINGFX

    Funds you sent to IMCTradingFX (imctradingfx.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.

    Trace summary — funds that left imctradingfx.com:

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

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

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

    Reading-list — chains and exchanges in scope:

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

    Lines the Professor will not cross:

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

    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

  • Office Hours on TIS

    // FROM THE CASEFILE — TIS

    TIS is a casefile under reading. The deposits to tisgltd.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 TIS:

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

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

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

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

    What the on-chain reading covers:

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

    Boundaries on every TIS casefile — never crossed:

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

  • TriumphIncome — Annotated by the Professor

    // FROM THE CASEFILE — TRIUMPHINCOME

    Funds you sent to TriumphIncome (triumphincome.io) 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.

    The annotation reads — wallet trace:

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

    Off-ramp summary — TriumphIncome casefile:

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

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

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

    What the on-chain reading covers:

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

    Lines the Professor will not cross:

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

    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

  • Professor’s Brief: Chronovalor

    // FROM THE CASEFILE — CHRONOVALOR

    Funds you sent to Chronovalor (chronovalor.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.

    The annotation reads — wallet trace:

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

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

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

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

    Chains and off-ramps the Professor follows:

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

    What is never asked of a claimant:

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

  • Professor’s Brief: Genix Markets

    // FROM THE CASEFILE — GENIX MARKETS

    Funds you sent to Genix Markets (genixmarkets.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.

    The annotation reads — wallet trace:

    • Deposit transaction hashes from the claimant wallet to the Genix 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 summary — Genix Markets casefile:

    • Genix 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 Genix 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 Genix Markets — the packet meets the off-ramp’s published compliance standard.
    • When the Genix 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 Genix Markets:

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

    Reading-list — chains and exchanges in scope:

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

    Recovery scammers do these things; the Professor never does:

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

  • Oriental FX — Annotated by the Professor

    // FROM THE CASEFILE — ORIENTAL FX

    When deposits to Oriental FX via orientalfx.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 orientalfx.com:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Oriental 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 reading — exchange counterparty for Oriental FX:

    • Endpoint counterparty in the Oriental 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.
    • Oriental 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 Oriental FX packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Oriental 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 pathway — how this casefile moves toward filing:

    1. Submission triage — Oriental FX casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — Oriental FX deposit and forwarding wallets captured.
    3. Endpoint identification — Oriental FX off-ramp wallet named.
    4. Filing — Oriental FX packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — Oriental FX stays on file until a documented next step is reached.

    What the Professor tracks across Oriental FX casefiles:

    • Chains the Oriental FX 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 Oriental FX — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the Oriental FX packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

    Recovery scammers do these things; the Professor never does:

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

    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