Trace summary — funds that left aman-trade.com:

• Deposit transaction hashes from the claimant wallet to the Aman Investment Group 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 Aman Investment Group casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Aman Investment Group’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty — the Aman Investment Group packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Aman Investment Group off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

Recovery pathway — how this casefile moves toward filing:

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

What the casefile records — chains and counterparties:

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

What the Professor will never do — by policy:

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

Trace summary — funds that left metamaxfx.co:

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

From the lectern — off-ramp identification:

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

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

Chains and off-ramps the Professor follows:

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

Boundaries on every MetaMaxFX casefile — never crossed:

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

The annotation reads — wallet trace:

• Initial deposit hashes to the Coinnova receiving address at coinnova.eu.
• 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 Coinnova:

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

The Professor’s recovery note for Coinnova:

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

What the on-chain reading covers:

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

Boundaries on every Coinnova casefile — never crossed:

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

The annotation reads — wallet trace:

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

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

Chains and off-ramps the Professor follows:

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

What is never asked of a claimant:

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

Trace summary — funds that left theactivetraders.com:

• Deposit transaction hashes from the claimant wallet to the The Active Traders 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.

The Professor’s off-ramp note:

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

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

What the casefile records — chains and counterparties:

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

Lines the Professor will not cross:

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

Wallet trace — what the Professor maps:

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

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

Recovery pathway — how this casefile moves toward filing:

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

Chains and off-ramps the Professor follows:

• Chains the CapexGo 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 CapexGo — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the CapexGo 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 CapexGo casefile — never request a seed phrase. Ever.
• On the CapexGo casefile — never request remote-access logins to a wallet or exchange.
• On the CapexGo casefile — never demand an upfront cash retainer to scope the matter.
• On the CapexGo casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the CapexGo casefile — never call the claimant unsolicited. Written-only.

Reading the wallets — 1PrimeOptions casefile:

• Deposit transaction hashes from the claimant wallet to the 1PrimeOptions 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.

The annotation continues — off-ramp endpoint:

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

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

What the casefile records — chains and counterparties:

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

What is never asked of a claimant:

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

On-chain reading — wallet flow for AW Markets:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for AW Markets.
• 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 map — where the funds left the chain:

• Endpoint counterparty in the AW 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.
• AW 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 AW Markets packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the AW 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.

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

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

What the Professor tracks across AW Markets casefiles:

• Chains the AW Markets 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 AW Markets — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the AW Markets 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 AW Markets — ask for a seed phrase.
• What the Professor will not do on AW Markets — request remote-access logins.
• What the Professor will not do on AW Markets — demand cash up front.
• What the Professor will not do on AW Markets — promise a guarantee.
• What the Professor will not do on AW Markets — call you out of the blue.

Wallet trace — what the Professor maps:

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

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

Recovery pathway — how this casefile moves toward filing:

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

Chains and off-ramps the Professor follows:

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

Recovery scammers do these things; the Professor never does:

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

The annotation reads — wallet trace:

• Claimant-to-platform deposit transactions on the deposit chain used by Octave Stock Trade.
• 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 reading — exchange counterparty for Octave Stock Trade:

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

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

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

Chains and off-ramps the Professor follows:

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

Lines the Professor will not cross:

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