Wallet trace — what the Professor maps:

• Deposit confirmations from the claimant to ULTIMATEFX’s receiving wallet at ultimatefxoption.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 Professor’s off-ramp note:

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

Chains and off-ramps the Professor follows:

• Chains the Professor reads for ULTIMATEFX casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in ULTIMATEFX — major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on ULTIMATEFX — 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:

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

Trace summary — funds that left edelraum.com:

• Initial deposit hashes to the Edelraum receiving address at edelraum.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 Edelraum casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Edelraum’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 Edelraum packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Edelraum off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

The Professor’s recovery note for Edelraum:

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

Chains and off-ramps the Professor follows:

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

Lines we never cross — by published policy:

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

Reading the wallets — Trade Room 24 casefile:

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

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

How a Trade Room 24 casefile becomes a regulator-ready filing:

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

What we read in a Trade Room 24 casefile:

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

Boundaries on every Trade Room 24 casefile — never crossed:

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

Wallet trace — what the Professor maps:

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

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

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

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

Reading-list — chains and exchanges in scope:

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

What the Professor will never do — by policy:

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

Trace summary — funds that left amiusgroupltd.com:

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

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

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

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

Reading-list — chains and exchanges in scope:

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

What is never asked of a claimant:

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

On-chain reading — wallet flow for Zentrox Trade:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for Zentrox Trade.
• 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 annotation continues — off-ramp endpoint:

• Zentrox Trade’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 Zentrox Trade off-ramp wallet against historical laundering throughput.
• The Zentrox Trade packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for Zentrox Trade, 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. Triage on Zentrox Trade — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on Zentrox Trade — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on Zentrox Trade — off-ramp endpoint matched to a named exchange counterparty.
4. File the Zentrox Trade 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 Zentrox Trade — the Professor stays on the casefile until a documented next step exists.

What the Professor tracks across Zentrox Trade casefiles:

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

Boundaries on every Zentrox Trade casefile — never crossed:

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

Reading the wallets — CGS International Securities casefile:

• Deposit confirmations from the claimant to CGS International Securities’s receiving wallet at cgsi.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:

• CGS International Securities off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The CGS International Securities 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 CGS International Securities — the packet meets the off-ramp’s published compliance standard.
• When the CGS International Securities 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 triage on CGS International Securities — the submission is read; a written assessment is delivered.
2. Forensic trace on CGS International Securities — every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification — the CGS International Securities endpoint is named.
4. Recovery filing on CGS International Securities — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of CGS International Securities — the Professor follows the casefile until next-step documentation exists.

What the casefile records — chains and counterparties:

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

Recovery scammers do these things; the Professor never does:

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

On-chain reading — wallet flow for CF Merchants:

• Deposit transaction hashes from the claimant wallet to the CF Merchants 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 — CF Merchants casefile:

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

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

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

What we read in a CF Merchants casefile:

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

Boundaries on every CF Merchants casefile — never crossed:

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

Trace summary — funds that left exodus.com:

• Deposit confirmations from the claimant to Exodus Movement Inc’s receiving wallet at exodus.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:

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

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

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

What the on-chain reading covers:

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

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

From the marginalia — the deposit pathway:

• Deposit-side hashes from claimant wallets into NATURAL SEVEN LIMITED’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 map — where the funds left the chain:

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

How a NATURAL SEVEN LIMITED casefile becomes a regulator-ready filing:

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

Chains and off-ramps the Professor follows:

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

Lines we never cross — by published policy:

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