The annotation reads, wallet trace:

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

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

What we read in a DAKS casefile:

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