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

Tag: report a scam

  • Power Markets — Annotated by the Professor

    // FROM THE CASEFILE — POWER MARKETS

    Funds you sent to Power Markets (power-markets.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.

    On-chain reading — wallet flow for Power Markets:

    • Deposit confirmations from the claimant to Power Markets’s receiving wallet at power-markets.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:

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

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

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

    Reading-list — chains and exchanges in scope:

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

    Lines the Professor will not cross:

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

    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

  • Reading the Chain: Trade Duac

    // FROM THE CASEFILE — TRADE DUAC

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

    • Deposit confirmations from the claimant to Trade Duac’s receiving wallet at tradeduac.co.
    • 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:

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

    The Professor’s recovery note for Trade Duac:

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

    Chains and off-ramps the Professor follows:

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

    Lines we never cross — by published policy:

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

  • Reading the Chain: Aurotrade24

    // FROM THE CASEFILE — AUROTRADE24

    Aurotrade24, operating from aurotrade24.com, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    Trace summary — funds that left aurotrade24.com:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the casefile records — chains and counterparties:

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

    Lines we never cross — by published policy:

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

    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: Sable Fx Global

    // FROM THE CASEFILE — SABLE FX GLOBAL

    Funds you sent to Sable Fx Global (sablefx.com;https:) 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.

    On-chain reading — wallet flow for Sable Fx Global:

    • Initial deposit hashes to the Sable Fx Global receiving address at sablefx.com;https:.
    • Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
    • Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
    • Obfuscation events through mixer contracts and privacy services.
    • Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

    Off-ramp reading — exchange counterparty for Sable Fx Global:

    • Sable Fx 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 Sable Fx 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 Sable Fx Global — the packet meets the off-ramp’s published compliance standard.
    • When the Sable Fx Global off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

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

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

    What the Professor tracks across Sable Fx Global casefiles:

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

    Boundaries on every Sable Fx Global casefile — never crossed:

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

  • Professor’s Brief: Fake IC Market Limited

    // FROM THE CASEFILE — FAKE IC MARKET LIMITED

    Fake IC Market Limited is a casefile under reading. The deposits to vip-marketsb.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.

    Reading the wallets — Fake IC Market Limited casefile:

    • Initial deposit hashes to the Fake IC Market Limited receiving address at vip-marketsb.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:

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

    The Professor’s recovery note for Fake IC Market Limited:

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

    Reading-list — chains and exchanges in scope:

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

    What is never asked of a claimant:

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

  • Reading the Chain: Regina Forex

    // FROM THE CASEFILE — REGINA FOREX

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

    Trace summary — funds that left reginaforex.com:

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

    From the lectern — off-ramp identification:

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

    How a Regina Forex casefile becomes a regulator-ready filing:

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

    What the casefile records — chains and counterparties:

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

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

  • Trenixo — Annotated by the Professor

    // FROM THE CASEFILE — TRENIXO

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

    Trace summary — funds that left trenixo.com:

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

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

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

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

    What the casefile records — chains and counterparties:

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

    Lines we never cross — by published policy:

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

  • Reading the Chain: Bitcoin 365

    // FROM THE CASEFILE — BITCOIN 365

    When a deposit ledgered to Bitcoin 365 at bitcoin-365.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 Bitcoin 365:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Bitcoin 365.
    • 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 map — where the funds left the chain:

    • Off-ramp endpoint for Bitcoin 365 resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Bitcoin 365’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Bitcoin 365 is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Bitcoin 365 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. Casefile triage on Bitcoin 365 — the submission is read; a written assessment is delivered.
    2. Forensic trace on Bitcoin 365 — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the Bitcoin 365 endpoint is named.
    4. Recovery filing on Bitcoin 365 — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of Bitcoin 365 — the Professor follows the casefile until next-step documentation exists.

    What we read in a Bitcoin 365 casefile:

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

    What the Professor will never do — by policy:

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

    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

  • Office Hours on MHT Holdings

    // FROM THE CASEFILE — MHT HOLDINGS

    MHT Holdings, operating from mhtholdings.org, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    From the marginalia — the deposit pathway:

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

    • Endpoint counterparty in the MHT Holdings casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • MHT Holdings’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 MHT Holdings packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the MHT Holdings off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

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

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

    What the casefile records — chains and counterparties:

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

    Lines we never cross — by published policy:

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

    // FROM THE CASEFILE — TRANZI

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

    • Deposit confirmations from the claimant to TRANZI’s receiving wallet at tranziinternational.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 reading — exchange counterparty for TRANZI:

    • Endpoint counterparty in the TRANZI casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • TRANZI’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 TRANZI packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the TRANZI off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

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

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

    What we read in a TRANZI casefile:

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

    Boundaries on every TRANZI casefile — never crossed:

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