The annotation reads, wallet trace:

• Initial deposit hashes to the Bitnexltd receiving address at bitnexltd.com.
• Hop-by-hop forwarding wallets across the deposit chain, captured with chain of custody hashes.
• Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
• Obfuscation events through mixer contracts and privacy services.
• Centralised-exchange off-ramp wallets, the named counterparty that holds compliance leverage.

Off-ramp reading, exchange counterparty for Bitnexltd:

• Bitnexltd’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage, typically named in the packet alongside the deposit address.
• Chain-analytics datasets cross-reference the Bitnexltd off-ramp wallet against historical laundering throughput.
• The Bitnexltd packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for Bitnexltd, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

Recovery pathway, how this casefile moves toward filing:

1. First read on Bitnexltd, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on Bitnexltd, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for Bitnexltd is named to a centralised exchange wallet.
4. Packet filing on Bitnexltd, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with Bitnexltd until a documented outcome or escalation step is on file.

Boundaries on every Bitnexltd casefile, never crossed:

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