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

Tag: scam help

  • Office Hours on Capital Management

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

    When deposits to Capital Management 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 Capital Management 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:

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

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

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

    Reading-list — chains and exchanges in scope:

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

    Capital Management has been flagged as a fake broker/platform by IOSCO I-SCAN (Singapore – Monetary Authority of Singapore). reported 2026-03-30. Jurisdiction: Singapore. 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/

  • Professor’s Brief: FXEDEAL

    // FROM THE CASEFILE — FXEDEAL

    When deposits to FXEDEAL via fxedeal.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:

    • Initial deposit hashes to the FXEDEAL receiving address at fxedeal.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:

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

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

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

    What the casefile records — chains and counterparties:

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

    Boundaries on every FXEDEAL casefile — never crossed:

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

  • Office Hours on Icarlatam

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

    When deposits to Icarlatam via icarlatam.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 transaction hashes from the claimant wallet to the Icarlatam 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:

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

    How a Icarlatam casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    Icarlatam has been flagged as a fake broker/platform by IOSCO I-SCAN (United States of America – Securities and Exchange Commission). reported 2026-06-04. Jurisdiction: United States of America. 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 tradingpal_ltd

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to tradingpal_ltd 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 tradingpal_ltd’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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

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

    tradingpal_ltd has been flagged as a fake broker/platform by IOSCO I-SCAN (Palestine – Palestine Capital Market Authority). reported 2025-08-01. Jurisdiction: Palestine. 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 KESHER GROUP_PANAMA

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

    When deposits to KESHER GROUP_PANAMA 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.

    Wallet trace — what the Professor maps:

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

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

    How a KESHER GROUP_PANAMA casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    KESHER GROUP_PANAMA has been flagged as a fake broker/platform by IOSCO I-SCAN (Panama – Superintendencia del Mercado de Valores). reported 2025-07-10. Jurisdiction: Panama. 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 Alpha Trust Management

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

    When deposits to Alpha Trust Management via alphatrustmanagement.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 transaction hashes from the claimant wallet to the Alpha Trust Management 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:

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

    How a Alpha Trust Management casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    Alpha Trust Management has been flagged as a fake broker/platform by IOSCO I-SCAN (Luxembourg – Commission de Surveillance du Secteur Financier). reported 2025-09-12. Jurisdiction: Luxembourg. 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/

  • goldfx — Annotated by the Professor

    // FROM THE CASEFILE — GOLDFX

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

    • Deposit transaction hashes from the claimant wallet to the goldfx 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 reading — exchange counterparty for goldfx:

    • goldfx’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 goldfx off-ramp wallet against historical laundering throughput.
    • The goldfx packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for goldfx, 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. Casefile review on goldfx — reading the submission against the no-go list.
    2. Trace mapping on goldfx — pathway documented to chain-of-custody standard.
    3. Off-ramp naming on goldfx — exchange endpoint identified.
    4. Packet filing on goldfx — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
    5. Documented follow-through on goldfx.

    What the casefile records — chains and counterparties:

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

    Lines the Professor will not cross:

    • goldfx policy — seed phrases are never requested.
    • goldfx policy — remote-access logins are never requested.
    • goldfx policy — no upfront cash retainer to scope.
    • goldfx policy — no guaranteed-recovery language. None.
    • goldfx policy — no unsolicited calls. The Professor responds in writing 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

  • Reading the Chain: HAWKENSLEY

    // FROM THE CASEFILE — HAWKENSLEY

    When a deposit ledgered to HAWKENSLEY at hawkensley.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 HAWKENSLEY:

    • Deposit-side hashes from claimant wallets into HAWKENSLEY’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 map — where the funds left the chain:

    • HAWKENSLEY’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 HAWKENSLEY off-ramp wallet against historical laundering throughput.
    • The HAWKENSLEY packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for HAWKENSLEY, 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 HAWKENSLEY:

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

    Reading-list — chains and exchanges in scope:

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

    Boundaries on every HAWKENSLEY casefile — never crossed:

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

  • Reading the Chain: MetrosityFX

    // FROM THE CASEFILE — METROSITYFX

    Funds you sent to MetrosityFX (metrosityfx.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 metrosityfx.com:

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

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

    The Professor’s recovery note for MetrosityFX:

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

    Reading-list — chains and exchanges in scope:

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

    Lines we never cross — by published policy:

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

    Open a free consultation

    Book a reading of your wallet — file at /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: Arcano Partners – ARCYIN–ARCCAP

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Arcano Partners – ARCYIN–ARCCAP 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.

    On-chain reading — wallet flow for Arcano Partners – ARCYIN–ARCCAP:

    • Claimant-to-platform deposit transactions on the deposit chain used by Arcano Partners – ARCYIN–ARCCAP.
    • 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 Arcano Partners – ARCYIN–ARCCAP:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

    Book a reading of your wallet — file at /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

    Why this platform is on our casefile

    Arcano Partners – ARCYIN–ARCCAP has been flagged as a fake broker/platform by IOSCO I-SCAN (Austria – Financial Market Authority). reported 2025-11-14. Jurisdiction: Austria. 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/