Reading the wallets — Fxorbitaltrade casefile:

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

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

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

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

What the Professor tracks across Fxorbitaltrade casefiles:

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

Recovery scammers do these things; the Professor never does:

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

Trace summary — funds that left offsetfx.com:

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

• Endpoint counterparty in the OffsetFX casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• OffsetFX’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 OffsetFX packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the OffsetFX 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. Submission triage — OffsetFX casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace — OffsetFX deposit and forwarding wallets captured.
3. Endpoint identification — OffsetFX off-ramp wallet named.
4. Filing — OffsetFX packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow — OffsetFX stays on file until a documented next step is reached.

What the casefile records — chains and counterparties:

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

Boundaries on every OffsetFX casefile — never crossed:

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

From the marginalia — the deposit pathway:

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

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

What we read in a Tradeinfy casefile:

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

Boundaries on every Tradeinfy casefile — never crossed:

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

Trace summary — funds that left euroinvestpartner.com:

• Deposit confirmations from the claimant to Euro Invest Partner’s receiving wallet at euroinvestpartner.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:

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

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

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

What the casefile records — chains and counterparties:

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

Lines we never cross — by published policy:

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

Reading the wallets — Quantafxai casefile:

• Initial deposit hashes to the Quantafxai receiving address at quantafxai.io.
• 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:

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

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

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

Reading-list — chains and exchanges in scope:

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

What is never asked of a claimant:

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

Trace summary — funds that left forexcitypro.com:

• Claimant-to-platform deposit transactions on the deposit chain used by Forexcitypro.
• 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 annotation continues — off-ramp endpoint:

• Forexcitypro’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 Forexcitypro off-ramp wallet against historical laundering throughput.
• The Forexcitypro packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for Forexcitypro, 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 Forexcitypro submission — written go/no-go returned.
2. Map the Forexcitypro wallet trail — every hop captured with chain-of-custody hashes.
3. Name the Forexcitypro off-ramp — endpoint counterparty identified.
4. Build and file the Forexcitypro recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the Forexcitypro file — until written next steps exist.

What we read in a Forexcitypro casefile:

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

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

Reading the wallets — Optimum Fx Pro casefile:

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

• Endpoint counterparty in the Optimum Fx Pro casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Optimum Fx Pro’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 Optimum Fx Pro packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Optimum Fx Pro 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. Casefile review on Optimum Fx Pro — reading the submission against the no-go list.
2. Trace mapping on Optimum Fx Pro — pathway documented to chain-of-custody standard.
3. Off-ramp naming on Optimum Fx Pro — exchange endpoint identified.
4. Packet filing on Optimum Fx Pro — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on Optimum Fx Pro.

What the casefile records — chains and counterparties:

• Chains tracked on Optimum Fx Pro — 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 Optimum Fx Pro — named exchange counterparties with public compliance contacts.
• Filings supported on Optimum Fx Pro — 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 Optimum Fx Pro casefile — never request a seed phrase. Ever.
• On the Optimum Fx Pro casefile — never request remote-access logins to a wallet or exchange.
• On the Optimum Fx Pro casefile — never demand an upfront cash retainer to scope the matter.
• On the Optimum Fx Pro casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the Optimum Fx Pro casefile — never call the claimant unsolicited. Written-only.

Wallet trace — what the Professor maps:

• Deposit transaction hashes from the claimant wallet to the OnyxProfit platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

From the lectern — off-ramp identification:

• Off-ramp endpoint for OnyxProfit resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• OnyxProfit’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for OnyxProfit is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the OnyxProfit 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. Submission triage — OnyxProfit casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace — OnyxProfit deposit and forwarding wallets captured.
3. Endpoint identification — OnyxProfit off-ramp wallet named.
4. Filing — OnyxProfit packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow — OnyxProfit stays on file until a documented next step is reached.

What the on-chain reading covers:

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

Recovery scammers do these things; the Professor never does:

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

Wallet trace — what the Professor maps:

• Deposit transaction hashes from the claimant wallet to the GMT platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

From the lectern — off-ramp identification:

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

How a GMT casefile becomes a regulator-ready filing:

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

Chains and off-ramps the Professor follows:

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

Lines we never cross — by published policy:

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

From the marginalia — the deposit pathway:

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

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

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

Chains and off-ramps the Professor follows:

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

What the Professor will never do — by policy:

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