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

  • 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

  • Office Hours on INVDaily

    // FROM THE CASEFILE — INVDAILY

    INVDaily, operating from invdaily.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 INVDaily 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:

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

    The Professor’s recovery note for INVDaily:

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

    What we read in a INVDaily casefile:

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

    Boundaries on every INVDaily casefile — never crossed:

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

  • Office Hours on MINING CRYPTO UNIVERSE

    // FROM THE CASEFILE — MINING CRYPTO UNIVERSE

    When deposits to MINING CRYPTO UNIVERSE via miningcryptouniverse.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.

    On-chain reading — wallet flow for MINING CRYPTO UNIVERSE:

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

    • MINING CRYPTO UNIVERSE’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 MINING CRYPTO UNIVERSE off-ramp wallet against historical laundering throughput.
    • The MINING CRYPTO UNIVERSE packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for MINING CRYPTO UNIVERSE, 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 triage on MINING CRYPTO UNIVERSE — the submission is read; a written assessment is delivered.
    2. Forensic trace on MINING CRYPTO UNIVERSE — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the MINING CRYPTO UNIVERSE endpoint is named.
    4. Recovery filing on MINING CRYPTO UNIVERSE — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of MINING CRYPTO UNIVERSE — the Professor follows the casefile until next-step documentation exists.

    What the Professor tracks across MINING CRYPTO UNIVERSE casefiles:

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

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: ShieldDEX

    // FROM THE CASEFILE — SHIELDDEX

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

    From the marginalia — the deposit pathway:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Boundaries on every ShieldDEX casefile — never crossed:

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

    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: Hive Markets

    // FROM THE CASEFILE — HIVE MARKETS

    Funds you sent to Hive Markets (hivemarkets.io) are still recorded on the public ledger; the question is no longer whether the money moved but where the off-ramp opened — and that is what the Professor reads.

    Wallet trace — what the Professor maps:

    • Claimant-to-platform deposit transactions on the deposit chain used by Hive Markets.
    • 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 Hive Markets casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Hive Markets’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 Hive Markets packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Hive Markets 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.

    The Professor’s recovery note for Hive Markets:

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

    Chains and off-ramps the Professor follows:

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

    What the Professor will never do — by policy:

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

    // FROM THE CASEFILE — FIRST CAPITALS

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

    Reading the wallets — First Capitals casefile:

    • Initial deposit hashes to the First Capitals receiving address at firstcapitals.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.

    Off-ramp summary — First Capitals casefile:

    • Off-ramp endpoint for First Capitals resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • First Capitals’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for First Capitals is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the First Capitals 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 First Capitals:

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

    What the casefile records — chains and counterparties:

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

    What the Professor will never do — by policy:

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

    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

  • From the Lectern: iTradingFX

    // FROM THE CASEFILE — ITRADINGFX

    iTradingFX is a casefile under reading. The deposits to itradingfx.net 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 — iTradingFX casefile:

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

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

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

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

    Chains and off-ramps the Professor follows:

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

    Lines the Professor will not cross:

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