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

  • Reading the Chain: Tickmilltrading.com

    // FROM THE CASEFILE — TICKMILLTRADING.COM

    Tickmilltrading.com is a casefile under reading. The deposits to tickmilltrading.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 Tickmilltrading.com:

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

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

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

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

    What the on-chain reading covers:

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

    Lines the Professor will not cross:

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

  • Reading the Chain: FastLinkFx

    // FROM THE CASEFILE — FASTLINKFX

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

    Wallet trace — what the Professor maps:

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

    Off-ramp map — where the funds left the chain:

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

    How a FastLinkFx casefile becomes a regulator-ready filing:

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

    What the casefile records — chains and counterparties:

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

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

    Open a free consultation

    Send the wallet for trace — /submit-a-case/ — the Professor responds in writing.

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: WFICorp

    // FROM THE CASEFILE — WFICORP

    Funds you sent to WFICorp (wficorp.co) 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.

    From the marginalia — the deposit pathway:

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

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

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

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

    Chains and off-ramps the Professor follows:

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

    Recovery scammers do these things; the Professor never does:

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

  • Office Hours on Olacco

    // FROM THE CASEFILE — OLACCO

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

    Reading the wallets — Olacco casefile:

    • Deposit-side hashes from claimant wallets into Olacco’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 Olacco:

    • Olacco’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 Olacco off-ramp wallet against historical laundering throughput.
    • The Olacco packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for Olacco, 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 Olacco:

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

    What the Professor tracks across Olacco casefiles:

    • Deposit-side chains in Olacco 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 Olacco packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Olacco — 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:

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

  • Professor’s Brief: Cryptos Circus

    // FROM THE CASEFILE — CRYPTOS CIRCUS

    Funds you sent to Cryptos Circus (cryptos-circus.com) are still recorded on the public ledger; the question is no longer whether the money moved but where the off-ramp opened — and that is what the Professor reads.

    From the marginalia — the deposit pathway:

    • Deposit-side hashes from claimant wallets into Cryptos Circus’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:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the Professor tracks across Cryptos Circus casefiles:

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

    Lines we never cross — by published policy:

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

  • Reading the Chain: TrustHub MiningFx

    // FROM THE CASEFILE — TRUSTHUB MININGFX

    When a deposit ledgered to TrustHub MiningFx at trusthubminingfx.com 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:

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

    The annotation continues — off-ramp endpoint:

    • TrustHub MiningFx off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The TrustHub MiningFx 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 TrustHub MiningFx — the packet meets the off-ramp’s published compliance standard.
    • When the TrustHub MiningFx 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. First read on TrustHub MiningFx — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on TrustHub MiningFx — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for TrustHub MiningFx is named to a centralised exchange wallet.
    4. Packet filing on TrustHub MiningFx — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with TrustHub MiningFx until a documented outcome or escalation step is on file.

    What the Professor tracks across TrustHub MiningFx casefiles:

    • Chains tracked on TrustHub MiningFx — 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 TrustHub MiningFx — named exchange counterparties with public compliance contacts.
    • Filings supported on TrustHub MiningFx — 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 TrustHub MiningFx — ask for a seed phrase.
    • What the Professor will not do on TrustHub MiningFx — request remote-access logins.
    • What the Professor will not do on TrustHub MiningFx — demand cash up front.
    • What the Professor will not do on TrustHub MiningFx — promise a guarantee.
    • What the Professor will not do on TrustHub MiningFx — call you out of the blue.

    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

  • Finance Cresthub — Annotated by the Professor

    // FROM THE CASEFILE — FINANCE CRESTHUB

    When deposits to Finance Cresthub via financecresthub.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 Finance Cresthub:

    • Deposit-side hashes from claimant wallets into Finance Cresthub’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 Finance Cresthub:

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

    How a Finance Cresthub casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    What is never asked of a claimant:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Lyreasf

    // FROM THE CASEFILE — LYREASF

    When deposits to Lyreasf via lyreasf.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:

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

    The annotation continues — off-ramp endpoint:

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

    How a Lyreasf casefile becomes a regulator-ready filing:

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

    What the casefile records — chains and counterparties:

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

    Lines the Professor will not cross:

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

  • AVS Brokers — Annotated by the Professor

    // FROM THE CASEFILE — AVS BROKERS

    AVS Brokers is a casefile under reading. The deposits to avsbrokers.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.

    The annotation reads — wallet trace:

    • Deposit-side hashes from claimant wallets into AVS Brokers’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 summary — AVS Brokers casefile:

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

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

    Chains and off-ramps the Professor follows:

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

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

  • From the Lectern: 99Stock Trades

    // FROM THE CASEFILE — 99STOCK TRADES

    Funds you sent to 99Stock Trades (99stocktrades.com) are still recorded on the public ledger; the question is no longer whether the money moved but where the off-ramp opened — and that is what the Professor reads.

    Wallet trace — what the Professor maps:

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

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

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

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

    What the casefile records — chains and counterparties:

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

    Recovery scammers do these things; the Professor never does:

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