Reading the wallets, F1 Capitals casefile:

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

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

Boundaries on every F1 Capitals casefile, never crossed:

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