From the marginalia — the deposit pathway:

• Initial deposit hashes to the PremiumTrade247 receiving address at premiumtrade247.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.

From the lectern — off-ramp identification:

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

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

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

What the casefile records — chains and counterparties:

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

Boundaries on every PremiumTrade247 casefile — never crossed:

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

On-chain reading — wallet flow for Hiyax Trading:

• Initial deposit hashes to the Hiyax Trading receiving address at hiyax.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 map — where the funds left the chain:

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

How a Hiyax Trading casefile becomes a regulator-ready filing:

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

Reading-list — chains and exchanges in scope:

• Chains the Professor reads for Hiyax Trading casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in Hiyax Trading — major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on Hiyax Trading — 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 Hiyax Trading casefile — never request a seed phrase. Ever.
• On the Hiyax Trading casefile — never request remote-access logins to a wallet or exchange.
• On the Hiyax Trading casefile — never demand an upfront cash retainer to scope the matter.
• On the Hiyax Trading casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the Hiyax Trading casefile — never call the claimant unsolicited. Written-only.

Reading the wallets — FXCL casefile:

• Deposit transaction hashes from the claimant wallet to the FXCL 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 FXCL casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• FXCL’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 FXCL packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the FXCL 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 FXCL — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on FXCL — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification — the off-ramp endpoint for FXCL is named to a centralised exchange wallet.
4. Packet filing on FXCL — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through — the Professor stays with FXCL until a documented outcome or escalation step is on file.

What the Professor tracks across FXCL casefiles:

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

What the Professor will never do — by policy:

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

From the marginalia — the deposit pathway:

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

From the lectern — off-ramp identification:

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

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

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

What the on-chain reading covers:

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

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

On-chain reading — wallet flow for Nanoquix:

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

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

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

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

What the casefile records — chains and counterparties:

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

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

From the marginalia — the deposit pathway:

• Deposit-side hashes from claimant wallets into Trade2wealthinvestment’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 annotation continues — off-ramp endpoint:

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

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

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

What the on-chain reading covers:

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

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

Trace summary — funds that left fastgrowtrade.com:

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

Off-ramp summary — Fast Grow Trade ltd casefile:

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

Reading-list — chains and exchanges in scope:

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

Boundaries on every Fast Grow Trade ltd casefile — never crossed:

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

From the marginalia — the deposit pathway:

• Deposit confirmations from the claimant to FalconCM’s receiving wallet at falcon-cm.net.
• 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 FalconCM:

• Off-ramp endpoint for FalconCM resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• FalconCM’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for FalconCM is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the FalconCM 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. Read the FalconCM submission — written go/no-go returned.
2. Map the FalconCM wallet trail — every hop captured with chain-of-custody hashes.
3. Name the FalconCM off-ramp — endpoint counterparty identified.
4. Build and file the FalconCM recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the FalconCM file — until written next steps exist.

Chains and off-ramps the Professor follows:

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

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

Wallet trace — what the Professor maps:

• Deposit-side hashes from claimant wallets into COPIER MARKETS TRADES OPTION’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 COPIER MARKETS TRADES OPTION:

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

The Professor’s recovery note for COPIER MARKETS TRADES OPTION:

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

What the casefile records — chains and counterparties:

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

Lines the Professor will not cross:

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

Trace summary — funds that left e-global-invests.xyz:

• Deposit transaction hashes from the claimant wallet to the e global invests 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 summary — e global invests casefile:

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

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

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

Reading-list — chains and exchanges in scope:

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

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