From the marginalia — the deposit pathway:

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

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

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

What we read in a Volatix Markets casefile:

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

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

From the marginalia — the deposit pathway:

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

• Endpoint counterparty in the Soho International casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Soho International’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 Soho International packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Soho International 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 triage on Soho International — the submission is read; a written assessment is delivered.
2. Forensic trace on Soho International — every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification — the Soho International endpoint is named.
4. Recovery filing on Soho International — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of Soho International — the Professor follows the casefile until next-step documentation exists.

Chains and off-ramps the Professor follows:

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

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

From the marginalia — the deposit pathway:

• Claimant-to-platform deposit transactions on the deposit chain used by Wealth ISA.
• 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 Professor’s off-ramp note:

• Off-ramp endpoint for Wealth ISA resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Wealth ISA’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Wealth ISA is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the Wealth ISA 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. Triage on Wealth ISA — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on Wealth ISA — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on Wealth ISA — off-ramp endpoint matched to a named exchange counterparty.
4. File the Wealth ISA 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 Wealth ISA — the Professor stays on the casefile until a documented next step exists.

Chains and off-ramps the Professor follows:

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

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

Trace summary — funds that left accuratefxearners.live:

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

• Off-ramp endpoint for Accurate FX Earner resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Accurate FX Earner’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Accurate FX Earner is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the Accurate FX Earner 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 triage on Accurate FX Earner — the submission is read; a written assessment is delivered.
2. Forensic trace on Accurate FX Earner — every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification — the Accurate FX Earner endpoint is named.
4. Recovery filing on Accurate FX Earner — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of Accurate FX Earner — the Professor follows the casefile until next-step documentation exists.

Reading-list — chains and exchanges in scope:

• Chains the Accurate FX Earner 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 Accurate FX Earner — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the Accurate FX Earner 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 we never cross — by published policy:

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

From the marginalia — the deposit pathway:

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

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

How a Luminex fx casefile becomes a regulator-ready filing:

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

What the casefile records — chains and counterparties:

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

Lines we never cross — by published policy:

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

From the marginalia — the deposit pathway:

• Claimant-to-platform deposit transactions on the deposit chain used by Oro Capital Group.
• 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 — Oro Capital Group casefile:

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

Reading-list — chains and exchanges in scope:

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

Lines we never cross — by published policy:

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

The annotation reads — wallet trace:

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

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

Recovery pathway — how this casefile moves toward filing:

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

What the Professor tracks across Forsythoilltd casefiles:

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

Recovery scammers do these things; the Professor never does:

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

On-chain reading — wallet flow for THRIVEPRIME FORUM INVESTMENTS:

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

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

The Professor’s recovery note for THRIVEPRIME FORUM INVESTMENTS:

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

Reading-list — chains and exchanges in scope:

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

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

On-chain reading — wallet flow for Bitwise Assets:

• Initial deposit hashes to the Bitwise Assets receiving address at bitwise-assets.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 reading — exchange counterparty for Bitwise Assets:

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

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

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

What the Professor tracks across Bitwise Assets casefiles:

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

Lines the Professor will not cross:

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

Wallet trace — what the Professor maps:

• Claimant-to-platform deposit transactions on the deposit chain used by Auxiliumfx.
• 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 map — where the funds left the chain:

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

How a Auxiliumfx casefile becomes a regulator-ready filing:

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

What the casefile records — chains and counterparties:

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

Lines the Professor will not cross:

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