The annotation reads — wallet trace:

• Initial deposit hashes to the FE Securities Limited receiving address at glfxhk.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 summary — FE Securities Limited casefile:

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

Chains and off-ramps the Professor follows:

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

Lines the Professor will not cross:

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

On-chain reading — wallet flow for Cidma CORP:

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

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

Reading-list — chains and exchanges in scope:

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

Recovery scammers do these things; the Professor never does:

• Boundary on Cidma CORP — seed phrases are off-limits.
• Boundary on Cidma CORP — remote logins are off-limits.
• Boundary on Cidma CORP — upfront cash retainers are off-limits.
• Boundary on Cidma CORP — guaranteed-recovery promises are off-limits.
• Boundary on Cidma CORP — 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 Progresive 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.

Off-ramp reading — exchange counterparty for Progresive Trade:

• Endpoint counterparty in the Progresive Trade casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Progresive Trade’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 Progresive Trade packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Progresive Trade 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. Read the Progresive Trade submission — written go/no-go returned.
2. Map the Progresive Trade wallet trail — every hop captured with chain-of-custody hashes.
3. Name the Progresive Trade off-ramp — endpoint counterparty identified.
4. Build and file the Progresive Trade recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the Progresive Trade file — until written next steps exist.

What the casefile records — chains and counterparties:

• Chains tracked on Progresive Trade — 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 Progresive Trade — named exchange counterparties with public compliance contacts.
• Filings supported on Progresive Trade — 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 Progresive Trade — ask for a seed phrase.
• What the Professor will not do on Progresive Trade — request remote-access logins.
• What the Professor will not do on Progresive Trade — demand cash up front.
• What the Professor will not do on Progresive Trade — promise a guarantee.
• What the Professor will not do on Progresive Trade — call you out of the blue.

Trace summary — funds that left swissnodtrade.com:

• Deposit-side hashes from claimant wallets into Swissnodtrade’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 summary — Swissnodtrade casefile:

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

Recovery pathway — how this casefile moves toward filing:

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

What the Professor tracks across Swissnodtrade casefiles:

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

Lines the Professor will not cross:

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

Trace summary — funds that left sc-vnd.com:

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

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

How a SOPHIE CAPITAL casefile becomes a regulator-ready filing:

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

What the casefile records — chains and counterparties:

• Chains the SOPHIE CAPITAL 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 SOPHIE CAPITAL — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the SOPHIE CAPITAL 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 SOPHIE CAPITAL casefile — never request a seed phrase. Ever.
• On the SOPHIE CAPITAL casefile — never request remote-access logins to a wallet or exchange.
• On the SOPHIE CAPITAL casefile — never demand an upfront cash retainer to scope the matter.
• On the SOPHIE CAPITAL casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the SOPHIE CAPITAL casefile — never call the claimant unsolicited. Written-only.

Trace summary — funds that left forextron-innovationmarket.online:

• Deposit-side hashes from claimant wallets into FOREXTRON Innovation Markets’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.

From the lectern — off-ramp identification:

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

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

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

What the Professor tracks across FOREXTRON Innovation Markets casefiles:

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

Boundaries on every FOREXTRON Innovation Markets casefile — never crossed:

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

From the marginalia — the deposit pathway:

• Deposit confirmations from the claimant to VIP Traders Club’s receiving wallet at viptradersclub.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 summary — VIP Traders Club casefile:

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

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

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

Chains and off-ramps the Professor follows:

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

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

Reading the wallets — CAPSTARFX casefile:

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

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

Recovery pathway — how this casefile moves toward filing:

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

What the casefile records — chains and counterparties:

• Chains the CAPSTARFX 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 CAPSTARFX — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the CAPSTARFX packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

What is never asked of a claimant:

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

Wallet trace — what the Professor maps:

• Deposit-side hashes from claimant wallets into TRESORFX’s receiving addresses.
• Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

The Professor’s off-ramp note:

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

Reading-list — chains and exchanges in scope:

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

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

Wallet trace — what the Professor maps:

• Initial deposit hashes to the RBFX receiving address at rbfx.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 Professor’s off-ramp note:

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

What the casefile records — chains and counterparties:

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

Lines the Professor will not cross:

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