The annotation reads, wallet trace:

• Claimant-to-platform deposit transactions on the deposit chain used by BlochainFXpayment.
• 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 summary, BlochainFXpayment casefile:

• Off-ramp endpoint for BlochainFXpayment resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• BlochainFXpayment’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for BlochainFXpayment is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the BlochainFXpayment 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. Submission triage, BlochainFXpayment casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, BlochainFXpayment deposit and forwarding wallets captured.
3. Endpoint identification, BlochainFXpayment off-ramp wallet named.
4. Filing, BlochainFXpayment packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, BlochainFXpayment stays on file until a documented next step is reached.

What we read in a BlochainFXpayment casefile:

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