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

Tag: investment scam

  • Casefile Qtmarkets — The Professor’s Note

    // FROM THE CASEFILE — QTMARKETS

    Qtmarkets is a casefile under reading. The deposits to qtmarkets-forex.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.

    Trace summary — funds that left qtmarkets-forex.com:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What we read in a Qtmarkets casefile:

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

    Recovery scammers do these things; the Professor never does:

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

  • Office Hours on Hubtrading

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to Hubtrading via https: 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 https::

    • Deposit confirmations from the claimant to Hubtrading’s receiving wallet at https:.
    • 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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Why this platform is on our casefile

    Hubtrading has been flagged as a fake broker/platform by IOSCO I-SCAN (Greece – Hellenic Capital Market Commission). reported 2026-07-02. Jurisdiction: Greece. 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/

  • Damarkets — Annotated by the Professor

    // FROM THE CASEFILE — DAMARKETS

    When deposits to Damarkets via damarketslimited.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.

    The annotation reads — wallet trace:

    • Deposit confirmations from the claimant to Damarkets’s receiving wallet at damarketslimited.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.

    The Professor’s off-ramp note:

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

    How a Damarkets casefile becomes a regulator-ready filing:

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

    What the on-chain reading covers:

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

    What is never asked of a claimant:

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

    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

  • From the Lectern: FXFellow

    // FROM THE CASEFILE — FXFELLOW

    When a deposit ledgered to FXFellow at fxfellow.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 deposit hashes — provided in the case submission and verified against the public ledger for FXFellow.
    • 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 FXFellow:

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

    How a FXFellow casefile becomes a regulator-ready filing:

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

    Chains and off-ramps the Professor follows:

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

    Lines we never cross — by published policy:

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

  • Office Hours on Fx Binary Option

    // FROM THE CASEFILE — FX BINARY OPTION

    The Professor opens the file on Fx Binary Option 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.

    The annotation reads — wallet trace:

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

    From the lectern — off-ramp identification:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Recovery scammers do these things; the Professor never does:

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

  • Office Hours on Daily Financial Earners

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

    When deposits to Daily Financial Earners 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 Daily Financial Earners 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:

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

    How a Daily Financial Earners casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    Daily Financial Earners has been flagged as a fake broker/platform by IOSCO I-SCAN (South Africa – Financial Sector Conduct Authority). reported 2026-06-05. Jurisdiction: South Africa. 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: YSHX

    // FROM THE CASEFILE — YSHX

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

    The annotation reads — wallet trace:

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

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

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

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

    What the Professor tracks across YSHX casefiles:

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

    What is never asked of a claimant:

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

  • Office Hours on Trdxinsight

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to Trdxinsight via https: 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 https::

    • Deposit confirmations from the claimant to Trdxinsight’s receiving wallet at https:.
    • 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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    Why this platform is on our casefile

    Trdxinsight has been flagged as a fake broker/platform by IOSCO I-SCAN (British Columbia – British Columbia Securities Commission). reported 2026-06-25. Jurisdiction: British Columbia. 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/

  • Office Hours on Tiqfx

    // FROM THE CASEFILE — TIQFX

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

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

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

    The Professor’s recovery note for Tiqfx:

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

    What the casefile records — chains and counterparties:

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

    What is never asked of a claimant:

    • What the Professor will not do on Tiqfx — ask for a seed phrase.
    • What the Professor will not do on Tiqfx — request remote-access logins.
    • What the Professor will not do on Tiqfx — demand cash up front.
    • What the Professor will not do on Tiqfx — promise a guarantee.
    • What the Professor will not do on Tiqfx — call you out of the blue.

    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

  • Reading the Chain: Agena Markets

    // FROM THE CASEFILE — AGENA MARKETS

    When deposits to Agena Markets via agenamarkets.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.

    The annotation reads — wallet trace:

    • Deposit confirmations from the claimant to Agena Markets’s receiving wallet at agenamarkets.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.

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

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

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

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

    What the Professor tracks across Agena Markets casefiles:

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

    Lines the Professor will not cross:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace