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: recover lost crypto

  • FinFinity Invest — Annotated by the Professor

    // FROM THE CASEFILE — FINFINITY INVEST

    When deposits to FinFinity Invest via finfinityinvest.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.

    From the marginalia — the deposit pathway:

    • Initial deposit hashes to the FinFinity Invest receiving address at finfinityinvest.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 reading — exchange counterparty for FinFinity Invest:

    • On the FinFinity Invest casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
    • The off-ramp wallet for FinFinity Invest is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the FinFinity Invest casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, FinFinity Invest escalates to IC3, state AG, and civil-discovery overlay.

    How a FinFinity Invest casefile becomes a regulator-ready filing:

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

    What the casefile records — chains and counterparties:

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

    Boundaries on every FinFinity Invest casefile — never crossed:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Capital Growth Market — Annotated by the Professor

    // FROM THE CASEFILE — CAPITAL GROWTH MARKET

    When deposits to Capital Growth Market via capitalgrowthmarket.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 Capital Growth Market:

    • Deposit confirmations from the claimant to Capital Growth Market’s receiving wallet at capitalgrowthmarket.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 Capital Growth Market:

    • Off-ramp endpoint for Capital Growth Market resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Capital Growth Market’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Capital Growth Market is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Capital Growth Market 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. Read the Capital Growth Market submission — written go/no-go returned.
    2. Map the Capital Growth Market wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the Capital Growth Market off-ramp — endpoint counterparty identified.
    4. Build and file the Capital Growth Market recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the Capital Growth Market file — until written next steps exist.

    What the Professor tracks across Capital Growth Market casefiles:

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

    What is never asked of a claimant:

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

    // FROM THE CASEFILE — OPTION TRADE LIVE FX

    When deposits to Option Trade Live Fx via opttradelivefx.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.

    Trace summary — funds that left opttradelivefx.com:

    • Deposit-side hashes from claimant wallets into Option Trade Live Fx’s receiving addresses.
    • Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
    • Inter-chain bridge transactions when value moves toward off-ramp liquidity.
    • Mixer/obfuscation events the operator routed through, where present.
    • Final off-ramp endpoint and named counterparty exchange.

    Off-ramp reading — exchange counterparty for Option Trade Live Fx:

    • Off-ramp endpoint for Option Trade Live Fx resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Option Trade Live Fx’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Option Trade Live Fx is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Option Trade Live Fx 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. First read on Option Trade Live Fx — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on Option Trade Live Fx — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for Option Trade Live Fx is named to a centralised exchange wallet.
    4. Packet filing on Option Trade Live Fx — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with Option Trade Live Fx until a documented outcome or escalation step is on file.

    Chains and off-ramps the Professor follows:

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

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Spectre.ai — Annotated by the Professor

    // FROM THE CASEFILE — SPECTRE.AI

    When deposits to Spectre.ai via spectre.ai 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.

    Reading the wallets — Spectre.ai casefile:

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

    The Professor’s off-ramp note:

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

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

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

    Chains and off-ramps the Professor follows:

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

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

    Open a free consultation

    The Professor reads claims at no charge to begin — open a consultation at /contact-us/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: BOOST CAPITAL ACADEMY

    // FROM THE CASEFILE — BOOST CAPITAL ACADEMY

    The Professor opens the file on BOOST CAPITAL ACADEMY 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.

    On-chain reading — wallet flow for BOOST CAPITAL ACADEMY:

    • Deposit-side hashes from claimant wallets into BOOST CAPITAL ACADEMY’s receiving addresses.
    • Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
    • Inter-chain bridge transactions when value moves toward off-ramp liquidity.
    • Mixer/obfuscation events the operator routed through, where present.
    • Final off-ramp endpoint and named counterparty exchange.

    Off-ramp reading — exchange counterparty for BOOST CAPITAL ACADEMY:

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

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

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

    What the casefile records — chains and counterparties:

    • Chains tracked on BOOST CAPITAL ACADEMY — 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 BOOST CAPITAL ACADEMY — named exchange counterparties with public compliance contacts.
    • Filings supported on BOOST CAPITAL ACADEMY — 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 BOOST CAPITAL ACADEMY casefile — never request a seed phrase. Ever.
    • On the BOOST CAPITAL ACADEMY casefile — never request remote-access logins to a wallet or exchange.
    • On the BOOST CAPITAL ACADEMY casefile — never demand an upfront cash retainer to scope the matter.
    • On the BOOST CAPITAL ACADEMY casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the BOOST CAPITAL ACADEMY 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

  • Casefile Royal Digital — The Professor’s Note

    // FROM THE CASEFILE — ROYAL DIGITAL

    Royal Digital, operating from royal-digital.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:

    • Initial deposit hashes to the Royal Digital receiving address at royal-digital.org.
    • 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:

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

    How a Royal Digital casefile becomes a regulator-ready filing:

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

    What the Professor tracks across Royal Digital casefiles:

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

    Recovery scammers do these things; the Professor never does:

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

  • Casefile InvestM — The Professor’s Note

    // FROM THE CASEFILE — INVESTM

    The Professor opens the file on InvestM the same way every casefile is opened — by treating the wallet history as text and the off-ramp endpoint as the citation a regulator can verify.

    The annotation reads — wallet trace:

    • Claimant-to-platform deposit transactions on the deposit chain used by InvestM.
    • Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
    • Cross-chain bridge events to chains with deeper exchange liquidity.
    • Privacy-service interactions, where present in the trail.
    • Off-ramp wallet — the named centralised-exchange endpoint.

    Off-ramp reading — exchange counterparty for InvestM:

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

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

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

    What the casefile records — chains and counterparties:

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

    Lines the Professor will not cross:

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

  • Casefile fxgrowth.online — The Professor’s Note

    // FROM THE CASEFILE — FXGROWTH.ONLINE

    When deposits to fxgrowth.online via fxgrowth.online go quiet, the on-chain record stays loud. The Professor’s reading begins where the platform’s silence does — with the wallet that received the funds and the path it took afterward.

    Wallet trace — what the Professor maps:

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

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

    What the on-chain reading covers:

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

    Lines the Professor will not cross:

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

  • Professor’s Brief: OXIAG

    // FROM THE CASEFILE — OXIAG

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

    Wallet trace — what the Professor maps:

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

    From the lectern — off-ramp identification:

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

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

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

    What the Professor tracks across OXIAG casefiles:

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

    What is never asked of a claimant:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: PRIMEFXT

    // FROM THE CASEFILE — PRIMEFXT

    When deposits to PRIMEFXT via primefxt.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.

    Trace summary — funds that left primefxt.com:

    • Deposit-side hashes from claimant wallets into PRIMEFXT’s receiving addresses.
    • Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
    • Inter-chain bridge transactions when value moves toward off-ramp liquidity.
    • Mixer/obfuscation events the operator routed through, where present.
    • Final off-ramp endpoint and named counterparty exchange.

    From the lectern — off-ramp identification:

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

    Recovery pathway — how this casefile moves toward filing:

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

    Chains and off-ramps the Professor follows:

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

    What is never asked of a claimant:

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