Wallet trace — what the Professor maps:

• Deposit-side hashes from claimant wallets into Capital Alpha Forgex’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 map — where the funds left the chain:

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

The Professor’s recovery note for Capital Alpha Forgex:

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

Reading-list — chains and exchanges in scope:

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

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

The annotation reads — wallet trace:

• Deposit confirmations from the claimant to Xelion’s receiving wallet at xeliionllimited.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 Professor’s off-ramp note:

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

What the Professor tracks across Xelion casefiles:

• Chains the Xelion 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 Xelion — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the Xelion 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:

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

The annotation reads — wallet trace:

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

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

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

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

What we read in a Tinkletrade Capital casefile:

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

What is never asked of a claimant:

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

Wallet trace — what the Professor maps:

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

Off-ramp reading — exchange counterparty for MT4 Markets:

• Endpoint counterparty in the MT4 Markets casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• MT4 Markets’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty — the MT4 Markets packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the MT4 Markets off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

How a MT4 Markets casefile becomes a regulator-ready filing:

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

What the Professor tracks across MT4 Markets casefiles:

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

Lines we never cross — by published policy:

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

Reading the wallets — Ghost Global Limited casefile:

• Deposit confirmations from the claimant to Ghost Global Limited’s receiving wallet at ghostgloballtd.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.

From the lectern — off-ramp identification:

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

What the Professor tracks across Ghost Global Limited casefiles:

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

Boundaries on every Ghost Global Limited casefile — never crossed:

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

Reading the wallets — Crystal Bitmining casefile:

• Deposit-side hashes from claimant wallets into Crystal Bitmining’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 map — where the funds left the chain:

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

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

What we read in a Crystal Bitmining casefile:

• Chains the Crystal Bitmining 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 Crystal Bitmining — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the Crystal Bitmining 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:

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

Trace summary — funds that left luminexfinance.com:

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

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

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

Chains and off-ramps the Professor follows:

• Deposit-side chains in Luminex finance 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 Luminex finance packets — centralised exchanges that accept regulator-grade compliance filings.
• Filing options on Luminex finance — 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 Luminex finance; the Professor never does — request seed phrases.
• Recovery scammers do these things on Luminex finance; the Professor never does — request remote logins.
• Recovery scammers do these things on Luminex finance; the Professor never does — demand upfront cash.
• Recovery scammers do these things on Luminex finance; the Professor never does — guarantee a recovery.
• Recovery scammers do these things on Luminex finance; the Professor never does — call you unsolicited.

Reading the wallets — ArgusStockBrokers casefile:

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

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

What we read in a ArgusStockBrokers casefile:

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

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

Reading the wallets — Angel Pro FX casefile:

• Deposit transaction hashes from the claimant wallet to the Angel Pro FX 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.

From the lectern — off-ramp identification:

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

How a Angel Pro FX casefile becomes a regulator-ready filing:

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

Chains and off-ramps the Professor follows:

• Chains the Angel Pro FX 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 Angel Pro FX — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the Angel Pro FX 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:

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

Reading the wallets — Wave Pro Trades casefile:

• Deposit confirmations from the claimant to Wave Pro Trades’s receiving wallet at waveprotrades.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.

From the lectern — off-ramp identification:

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

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

What the on-chain reading covers:

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

What the Professor will never do — by policy:

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