On-chain reading, wallet flow for Dynasty Trade:

• Initial deposit hashes to the Dynasty Trade receiving address at dynasty-trade.io.
• 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 map, where the funds left the chain:

• Endpoint counterparty in the Dynasty Trade casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Dynasty Trade’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty, the Dynasty Trade packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Dynasty Trade off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

How a Dynasty Trade casefile becomes a evidence filing:

1. Read the Dynasty Trade submission, written go/no-go returned.
2. Map the Dynasty Trade wallet trail, every hop captured with chain of custody hashes.
3. Name the Dynasty Trade off-ramp, endpoint counterparty identified.
4. Build and file the Dynasty Trade recovery packet, to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the Dynasty Trade file, until written next steps exist.

What the casefile records, chains and counterparties:

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