Reading the wallets — Fintex Pro casefile:

• Deposit confirmations from the claimant to Fintex Pro’s receiving wallet at fintexpro.co.
• 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 Fintex 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.
• Fintex 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 Fintex Pro packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Fintex 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.

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

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

What we read in a Fintex Pro casefile:

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

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

Reading the wallets — Forex24 Market casefile:

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

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

How a Forex24 Market casefile becomes a regulator-ready filing:

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

What the Professor tracks across Forex24 Market casefiles:

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

Lines we never cross — by published policy:

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

On-chain reading — wallet flow for UpSideStake:

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

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

Chains and off-ramps the Professor follows:

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

What is never asked of a claimant:

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

Trace summary — funds that left amicusmarketsfx.com:

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

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

How a Amicus Finance Limited casefile becomes a regulator-ready filing:

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

Reading-list — chains and exchanges in scope:

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

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

Reading the wallets — Tradigrowthfyxpro casefile:

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

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

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

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

What the Professor tracks across Tradigrowthfyxpro casefiles:

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

What is never asked of a claimant:

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

Reading the wallets — GKM Global Tech casefile:

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

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

How a GKM Global Tech casefile becomes a regulator-ready filing:

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

What the on-chain reading covers:

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

Lines we never cross — by published policy:

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

Trace summary — funds that left cointradest.top:

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

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

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

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

What we read in a Cointrade.top casefile:

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

Lines we never cross — by published policy:

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

Wallet trace — what the Professor maps:

• Initial deposit hashes to the ZQFX receiving address at zqfx.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 annotation continues — off-ramp endpoint:

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

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

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

What we read in a ZQFX casefile:

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

Recovery scammers do these things; the Professor never does:

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

From the marginalia — the deposit pathway:

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

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

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

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

Chains and off-ramps the Professor follows:

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

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

From the marginalia — the deposit pathway:

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

• SureShotFX’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 SureShotFX off-ramp wallet against historical laundering throughput.
• The SureShotFX packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for SureShotFX, 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. First read on SureShotFX — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on SureShotFX — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification — the off-ramp endpoint for SureShotFX is named to a centralised exchange wallet.
4. Packet filing on SureShotFX — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through — the Professor stays with SureShotFX until a documented outcome or escalation step is on file.

Chains and off-ramps the Professor follows:

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

Lines we never cross — by published policy:

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