From the marginalia, the deposit pathway:

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

Off-ramp map, where the funds left the chain:

• Off-ramp endpoint for ABN Markets resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• ABN Markets’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for ABN Markets is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the ABN Markets 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. Casefile triage on ABN Markets, the submission is read; a written assessment is delivered.
2. Forensic trace on ABN Markets, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the ABN Markets endpoint is named.
4. Recovery filing on ABN Markets, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of ABN Markets, the Professor follows the casefile until next-step documentation exists.