From the marginalia, the deposit pathway:

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

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

The Professor’s recovery note for FTSFX:

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