The annotation reads — wallet trace:

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

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

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

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

What we read in a UCMarkets casefile:

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

Boundaries on every UCMarkets casefile — never crossed:

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

Reading the wallets — PDMBulls casefile:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for PDMBulls.
• Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

Off-ramp summary — PDMBulls casefile:

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

The Professor’s recovery note for PDMBulls:

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

What we read in a PDMBulls casefile:

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

Boundaries on every PDMBulls casefile — never crossed:

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

From the marginalia — the deposit pathway:

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

The Professor’s off-ramp note:

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

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

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

What the on-chain reading covers:

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

What is never asked of a claimant:

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

Wallet trace — what the Professor maps:

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

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

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

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

What we read in a EO Broker casefile:

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

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

On-chain reading — wallet flow for AIFundBTC:

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

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

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

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

Chains and off-ramps the Professor follows:

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

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

Reading the wallets — AssegAi FX casefile:

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

From the lectern — off-ramp identification:

• AssegAi FX’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 AssegAi FX off-ramp wallet against historical laundering throughput.
• The AssegAi FX packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for AssegAi FX, 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. Submission triage — AssegAi FX casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace — AssegAi FX deposit and forwarding wallets captured.
3. Endpoint identification — AssegAi FX off-ramp wallet named.
4. Filing — AssegAi FX packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow — AssegAi FX stays on file until a documented next step is reached.

Chains and off-ramps the Professor follows:

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

What is never asked of a claimant:

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

On-chain reading — wallet flow for EVO GLOBAL TRADE:

• Deposit confirmations from the claimant to EVO GLOBAL TRADE’s receiving wallet at evoglobaltrade.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:

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

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

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

What we read in a EVO GLOBAL TRADE casefile:

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

Boundaries on every EVO GLOBAL TRADE casefile — never crossed:

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

From the marginalia — the deposit pathway:

• Claimant-to-platform deposit transactions on the deposit chain used by Wealth ISA.
• 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 Professor’s off-ramp note:

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

Chains and off-ramps the Professor follows:

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

Boundaries on every Wealth ISA casefile — never crossed:

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

From the marginalia — the deposit pathway:

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

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

How a Luminex fx casefile becomes a regulator-ready filing:

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

What the casefile records — chains and counterparties:

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

Lines we never cross — by published policy:

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

From the marginalia — the deposit pathway:

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

Off-ramp summary — Oro Capital Group casefile:

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

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

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

Reading-list — chains and exchanges in scope:

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

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