The annotation reads, wallet trace:

• Claimant-to-platform deposit transactions on the deposit chain used by TargetFX.
• 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 reading, exchange counterparty for TargetFX:

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

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

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

Boundaries on every TargetFX casefile, never crossed:

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