The annotation reads — wallet trace:

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

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

How a YUB Prime casefile becomes a regulator-ready filing:

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

What the casefile records — chains and counterparties:

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

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

From the marginalia — the deposit pathway:

• Claimant-to-platform deposit transactions on the deposit chain used by True North Options.
• 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 summary — True North Options casefile:

• True North Options off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The True North Options 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 True North Options — the packet meets the off-ramp’s published compliance standard.
• When the True North Options 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. Triage on True North Options — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on True North Options — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on True North Options — off-ramp endpoint matched to a named exchange counterparty.
4. File the True North Options 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 True North Options — the Professor stays on the casefile until a documented next step exists.

What the on-chain reading covers:

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

Recovery scammers do these things; the Professor never does:

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

From the marginalia — the deposit pathway:

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

From the lectern — off-ramp identification:

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

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

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

What the on-chain reading covers:

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

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

The annotation reads — wallet trace:

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

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

The Professor’s recovery note for Legacy FX Brokers:

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

What the on-chain reading covers:

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

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

From the marginalia — the deposit pathway:

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

• Phoenix Brokage’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 Phoenix Brokage off-ramp wallet against historical laundering throughput.
• The Phoenix Brokage packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for Phoenix Brokage, 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. Casefile review on Phoenix Brokage — reading the submission against the no-go list.
2. Trace mapping on Phoenix Brokage — pathway documented to chain-of-custody standard.
3. Off-ramp naming on Phoenix Brokage — exchange endpoint identified.
4. Packet filing on Phoenix Brokage — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on Phoenix Brokage.

What we read in a Phoenix Brokage casefile:

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

What the Professor will never do — by policy:

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

On-chain reading — wallet flow for FiatVisions:

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

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

The Professor’s recovery note for FiatVisions:

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

What the Professor tracks across FiatVisions casefiles:

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

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

The annotation reads — wallet trace:

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

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

Recovery pathway — how this casefile moves toward filing:

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

Chains and off-ramps the Professor follows:

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

Boundaries on every Tradeshark24 casefile — never crossed:

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

Wallet trace — what the Professor maps:

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

The Professor’s off-ramp note:

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

What the on-chain reading covers:

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

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

Trace summary — funds that left deluxeplustrade.com:

• Initial deposit hashes to the DeluxePlusTrade receiving address at deluxeplustrade.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:

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

What we read in a DeluxePlusTrade casefile:

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

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

Trace summary — funds that left apex-cryptofx.com:

• Claimant-to-platform deposit transactions on the deposit chain used by Apex Crypto FX.
• 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 summary — Apex Crypto FX casefile:

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

What the casefile records — chains and counterparties:

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

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