On-chain reading, wallet flow for FXCT Investment:

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

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

How a FXCT Investment casefile becomes a evidence filing:

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

Lines the Professor will not cross:

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