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

Tag: scam help

  • CCrypto — Annotated by the Professor

    // FROM THE CASEFILE — CCRYPTO

    When deposits to CCrypto via ccrypto.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.

    From the marginalia — the deposit pathway:

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

    • CCrypto off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The CCrypto 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 CCrypto — the packet meets the off-ramp’s published compliance standard.
    • When the CCrypto 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. Read the CCrypto submission — written go/no-go returned.
    2. Map the CCrypto wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the CCrypto off-ramp — endpoint counterparty identified.
    4. Build and file the CCrypto recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the CCrypto file — until written next steps exist.

    What the casefile records — chains and counterparties:

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

    Lines the Professor will not cross:

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

    // FROM THE CASEFILE — DIAMONDWHALE

    DiamondWhale is a casefile under reading. The deposits to diamondwhale.pro 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.

    The annotation reads — wallet trace:

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

    • DiamondWhale’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 DiamondWhale off-ramp wallet against historical laundering throughput.
    • The DiamondWhale packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for DiamondWhale, 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. Triage on DiamondWhale — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on DiamondWhale — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on DiamondWhale — off-ramp endpoint matched to a named exchange counterparty.
    4. File the DiamondWhale 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 DiamondWhale — the Professor stays on the casefile until a documented next step exists.

    What the Professor tracks across DiamondWhale casefiles:

    • Chains the DiamondWhale casefile may touch — Bitcoin and Ethereum at the deposit side, Tron USDT-TRC20 in stablecoin pathways, BNB Smart Chain and the L2s (Arbitrum, Optimism, Polygon, Base) where bridges link them.
    • Off-ramps relevant to DiamondWhale — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the DiamondWhale packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

    What the Professor will never do — by policy:

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

  • Reading the Chain: TradesVisions

    // FROM THE CASEFILE — TRADESVISIONS

    TradesVisions, operating from tradesvisions.co, 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 TradesVisions receiving address at tradesvisions.co.
    • 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:

    • TradesVisions’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 TradesVisions off-ramp wallet against historical laundering throughput.
    • The TradesVisions packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for TradesVisions, 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. First read on TradesVisions — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on TradesVisions — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for TradesVisions is named to a centralised exchange wallet.
    4. Packet filing on TradesVisions — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with TradesVisions until a documented outcome or escalation step is on file.

    What the Professor tracks across TradesVisions casefiles:

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

    Lines the Professor will not cross:

    • Recovery scammers do these things on TradesVisions; the Professor never does — request seed phrases.
    • Recovery scammers do these things on TradesVisions; the Professor never does — request remote logins.
    • Recovery scammers do these things on TradesVisions; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on TradesVisions; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on TradesVisions; 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: Clone CPT

    // FROM THE CASEFILE — CLONE CPT

    When deposits to Clone CPT via cptmarketsig.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 Clone CPT:

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

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

    The Professor’s recovery note for Clone CPT:

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

    What the casefile records — chains and counterparties:

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

    What is never asked of a claimant:

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

    Open a free consultation

    Submit your wallet for a forensic reading — /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile PJP Invest — The Professor’s Note

    // FROM THE CASEFILE — PJP INVEST

    The Professor opens the file on PJP Invest 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 PJP Invest.
    • 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:

    • On the PJP 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 PJP 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 PJP Invest casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, PJP Invest escalates to IC3, state AG, and civil-discovery overlay.

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

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

    Chains and off-ramps the Professor follows:

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

    Recovery scammers do these things; the Professor never does:

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

  • Office Hours on Clone Apollo LTD

    // FROM THE CASEFILE — CLONE APOLLO LTD

    Funds you sent to Clone Apollo LTD (fxapollo.com;https:) are still recorded on the public ledger; the question is no longer whether the money moved but where the off-ramp opened — and that is what the Professor reads.

    On-chain reading — wallet flow for Clone Apollo LTD:

    • Deposit confirmations from the claimant to Clone Apollo LTD’s receiving wallet at fxapollo.com;https:.
    • Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
    • Cross-chain bridge transactions where the operator routed value out of the deposit chain.
    • Mixer or coin-join interactions, where applicable.
    • Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

    From the lectern — off-ramp identification:

    • Clone Apollo LTD casefiles end at a centralised exchange — Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
    • Off-ramp wallet for Clone Apollo LTD is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for Clone Apollo LTD — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Clone Apollo LTD casefile.

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

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

    Reading-list — chains and exchanges in scope:

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

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

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

    // FROM THE CASEFILE — AVAXFX MARKETS

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

    From the marginalia — the deposit pathway:

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

    The annotation continues — off-ramp endpoint:

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

    The Professor’s recovery note for AvaxFX Markets:

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

    What the Professor tracks across AvaxFX Markets casefiles:

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

    • Recovery scammers do these things on AvaxFX Markets; the Professor never does — request seed phrases.
    • Recovery scammers do these things on AvaxFX Markets; the Professor never does — request remote logins.
    • Recovery scammers do these things on AvaxFX Markets; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on AvaxFX Markets; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on AvaxFX Markets; 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 Menta Credex

    // FROM THE CASEFILE — MENTA CREDEX

    Menta Credex is a casefile under reading. The deposits to mentacredex.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 Menta Credex:

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

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

    The Professor’s recovery note for Menta Credex:

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

    What the casefile records — chains and counterparties:

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

    Boundaries on every Menta Credex casefile — never crossed:

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

  • Reading the Chain: Aztec Group

    // FROM THE CASEFILE — AZTEC GROUP

    Funds you sent to Aztec Group (aztecgroup.cfd) 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.

    Reading the wallets — Aztec Group casefile:

    • Deposit confirmations from the claimant to Aztec Group’s receiving wallet at aztecgroup.cfd.
    • 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 Aztec Group casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Aztec Group’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 Aztec Group packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Aztec Group 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 Aztec Group:

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

    Chains and off-ramps the Professor follows:

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

    What the Professor will never do — by policy:

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

    Open a free consultation

    Submit your wallet for a forensic reading — /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Eva Trades

    // FROM THE CASEFILE — EVA TRADES

    Eva Trades is a casefile under reading. The deposits to evatrades.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.

    Trace summary — funds that left evatrades.com:

    • Deposit-side hashes from claimant wallets into Eva Trades’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.

    The Professor’s off-ramp note:

    • Off-ramp endpoint for Eva Trades resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Eva Trades’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Eva Trades is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Eva Trades 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. Triage on Eva Trades — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on Eva Trades — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on Eva Trades — off-ramp endpoint matched to a named exchange counterparty.
    4. File the Eva Trades 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 Eva Trades — the Professor stays on the casefile until a documented next step exists.

    What the on-chain reading covers:

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

    Boundaries on every Eva Trades casefile — never crossed:

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

    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