On-chain reading, wallet flow for Centaur500:

• Initial deposit hashes to the Centaur500 receiving address at centaur500.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 summary, Centaur500 casefile:

• Centaur500’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 Centaur500 off-ramp wallet against historical laundering throughput.
• The Centaur500 packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for Centaur500, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

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

1. Casefile review on Centaur500, reading the submission against the no-go list.
2. Trace mapping on Centaur500, pathway documented to chain of custody standard.
3. Off-ramp naming on Centaur500, exchange endpoint identified.
4. Packet filing on Centaur500, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on Centaur500.