On-chain reading — wallet flow for FMA Global Trade:

• Deposit confirmations from the claimant to FMA Global Trade’s receiving wallet at fmaglobaltrade.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 FMA Global Trade:

• FMA Global Trade off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The FMA Global Trade 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 FMA Global Trade — the packet meets the off-ramp’s published compliance standard.
• When the FMA Global Trade 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. Casefile review on FMA Global Trade — reading the submission against the no-go list.
2. Trace mapping on FMA Global Trade — pathway documented to chain-of-custody standard.
3. Off-ramp naming on FMA Global Trade — exchange endpoint identified.
4. Packet filing on FMA Global Trade — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on FMA Global Trade.

What the Professor tracks across FMA Global Trade casefiles:

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

What is never asked of a claimant:

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

The annotation reads — wallet trace:

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

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

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

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

What we read in a Net Capital Globe casefile:

• Deposit-side chains in Net Capital Globe 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 Net Capital Globe packets — centralised exchanges that accept regulator-grade compliance filings.
• Filing options on Net Capital Globe — 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 Net Capital Globe casefile — never request a seed phrase. Ever.
• On the Net Capital Globe casefile — never request remote-access logins to a wallet or exchange.
• On the Net Capital Globe casefile — never demand an upfront cash retainer to scope the matter.
• On the Net Capital Globe casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the Net Capital Globe casefile — never call the claimant unsolicited. Written-only.

Trace summary — funds that left thefxplayer.com:

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

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

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

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

What we read in a FxPlayer casefile:

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

Lines we never cross — by published policy:

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

Reading the wallets — 360FXTraders casefile:

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

• Off-ramp endpoint for 360FXTraders resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• 360FXTraders’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for 360FXTraders is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the 360FXTraders 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 360FXTraders:

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

What the Professor tracks across 360FXTraders casefiles:

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

What the Professor will never do — by policy:

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

The annotation reads — wallet trace:

• Deposit transaction hashes from the claimant wallet to the Prism Capital Markets 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 map — where the funds left the chain:

• Endpoint counterparty in the Prism Capital 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.
• Prism Capital 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 Prism Capital Markets packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Prism Capital 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 Prism Capital Markets casefile becomes a regulator-ready filing:

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

Reading-list — chains and exchanges in scope:

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

Trace summary — funds that left najmcapital.com:

• Initial deposit hashes to the NAJM Capital receiving address at najmcapital.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 summary — NAJM Capital casefile:

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

The Professor’s recovery note for NAJM Capital:

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

What the Professor tracks across NAJM Capital casefiles:

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

Boundaries on every NAJM Capital casefile — never crossed:

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

The annotation reads — wallet trace:

• Deposit transaction hashes from the claimant wallet to the Elite Broker 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 map — where the funds left the chain:

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

How a Elite Broker casefile becomes a regulator-ready filing:

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

What the casefile records — chains and counterparties:

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

Recovery scammers do these things; the Professor never does:

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

Reading the wallets — Invest Vital casefile:

• Initial deposit hashes to the Invest Vital receiving address at investvital.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:

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

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

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

What the casefile records — chains and counterparties:

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

Boundaries on every Invest Vital casefile — never crossed:

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

The annotation reads — wallet trace:

• Initial deposit hashes to the CM Prime receiving address at cm-prime.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:

• Off-ramp endpoint for CM Prime resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• CM Prime’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for CM Prime is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the CM Prime 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 review on CM Prime — reading the submission against the no-go list.
2. Trace mapping on CM Prime — pathway documented to chain-of-custody standard.
3. Off-ramp naming on CM Prime — exchange endpoint identified.
4. Packet filing on CM Prime — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on CM Prime.

What the casefile records — chains and counterparties:

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

Recovery scammers do these things; the Professor never does:

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

On-chain reading — wallet flow for GS Capital:

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

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

The Professor’s recovery note for GS Capital:

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

What the casefile records — chains and counterparties:

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

Lines we never cross — by published policy:

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