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

Tag: scam broker

  • Reading the Chain: World Global Investment

    // FROM THE CASEFILE — WORLD GLOBAL INVESTMENT

    World Global Investment, operating from worldglobal.ng, 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:

    • Claimant-to-platform deposit transactions on the deposit chain used by World Global Investment.
    • 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 map — where the funds left the chain:

    • Endpoint counterparty in the World Global Investment casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • World Global Investment’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 World Global Investment packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the World Global Investment 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. Casefile triage on World Global Investment — the submission is read; a written assessment is delivered.
    2. Forensic trace on World Global Investment — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the World Global Investment endpoint is named.
    4. Recovery filing on World Global Investment — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of World Global Investment — the Professor follows the casefile until next-step documentation exists.

    Chains and off-ramps the Professor follows:

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

    Lines the Professor will not cross:

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

    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 Tradedu

    // FROM THE CASEFILE — TRADEDU

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

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

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

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

    Reading-list — chains and exchanges in scope:

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

    Recovery scammers do these things; the Professor never does:

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

    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: TradeZoom

    // FROM THE CASEFILE — TRADEZOOM

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

    The annotation reads — wallet trace:

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

    • TradeZoom off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The TradeZoom 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 TradeZoom — the packet meets the off-ramp’s published compliance standard.
    • When the TradeZoom 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. Triage on TradeZoom — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on TradeZoom — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on TradeZoom — off-ramp endpoint matched to a named exchange counterparty.
    4. File the TradeZoom 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 TradeZoom — the Professor stays on the casefile until a documented next step exists.

    What the Professor tracks across TradeZoom casefiles:

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

    Lines we never cross — by published policy:

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

    Open a free consultation

    Bring the casefile to office hours — open a free consultation at /contact-us/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Professor’s Brief: Hedgecap Limited

    // FROM THE CASEFILE — HEDGECAP LIMITED

    Hedgecap Limited is a casefile under reading. The deposits to hedgecaplimited.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 — Hedgecap Limited casefile:

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

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

    How a Hedgecap Limited casefile becomes a regulator-ready filing:

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

    What we read in a Hedgecap Limited casefile:

    • Chains tracked on Hedgecap Limited — 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 Hedgecap Limited — named exchange counterparties with public compliance contacts.
    • Filings supported on Hedgecap Limited — 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:

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

    // FROM THE CASEFILE — MYTRADEMATE

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

    The annotation reads — wallet trace:

    • Deposit transaction hashes from the claimant wallet to the MyTradeMate platform receiving address.
    • Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
    • Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
    • Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
    • Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

    The annotation continues — off-ramp endpoint:

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

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

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

    What the casefile records — chains and counterparties:

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

    What is never asked of a claimant:

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

    Open a free consultation

    Open a free first consultation — /contact-us/ — written response within one business day.

    Open a Free Case Consultation   Submit Wallet for Trace

  • bitfxpro.us — Annotated by the Professor

    // FROM THE CASEFILE — BITFXPRO.US

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

    Reading the wallets — bitfxpro.us casefile:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    What the Professor will never do — by policy:

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

    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 UP MARKETS

    // FROM THE CASEFILE — UP MARKETS

    UP MARKETS is a casefile under reading. The deposits to up-markets.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.

    Wallet trace — what the Professor maps:

    • Initial deposit hashes to the UP MARKETS receiving address at up-markets.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 Professor’s off-ramp note:

    • UP MARKETS off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The UP MARKETS off-ramp address is matched to known compliance feeds — the Professor’s standing dataset plus chain-analytics references.
    • Compliance leverage is applied at the named counterparty for UP MARKETS — the packet meets the off-ramp’s published compliance standard.
    • When the UP MARKETS off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

    How a UP MARKETS casefile becomes a regulator-ready filing:

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

    What the on-chain reading covers:

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

    Boundaries on every UP MARKETS casefile — never crossed:

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

    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

  • Professor’s Brief: Universal Global FX

    // FROM THE CASEFILE — UNIVERSAL GLOBAL FX

    Universal Global FX is a casefile under reading. The deposits to universalglobalfx.com sit on-chain, immutable; the wallet pathway is the primary source, and the off-ramp endpoint is the conclusion the Professor’s marginalia points toward.

    On-chain reading — wallet flow for Universal Global FX:

    • Claimant-to-platform deposit transactions on the deposit chain used by Universal Global FX.
    • 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 map — where the funds left the chain:

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

    How a Universal Global FX casefile becomes a regulator-ready filing:

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

    Chains and off-ramps the Professor follows:

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

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

  • Fx Trade Pro — Annotated by the Professor

    // FROM THE CASEFILE — FX TRADE PRO

    When a deposit ledgered to Fx Trade Pro at fxtradepro.net stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    The annotation reads — wallet trace:

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

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

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

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

    What the casefile records — chains and counterparties:

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

    Boundaries on every Fx Trade Pro casefile — never crossed:

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

  • Casefile SuperFin — The Professor’s Note

    // FROM THE CASEFILE — SUPERFIN

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

    Trace summary — funds that left superfinfx.com:

    • Deposit transaction hashes from the claimant wallet to the SuperFin 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 map — where the funds left the chain:

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

    How a SuperFin casefile becomes a regulator-ready filing:

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

    What the on-chain reading covers:

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

    What is never asked of a claimant:

    • SuperFin policy — seed phrases are never requested.
    • SuperFin policy — remote-access logins are never requested.
    • SuperFin policy — no upfront cash retainer to scope.
    • SuperFin policy — no guaranteed-recovery language. None.
    • SuperFin policy — no unsolicited calls. The Professor responds in writing only.

    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