The annotation reads, wallet trace:

• Initial deposit hashes to the MatrixTrade receiving address at matrixtrade.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.

The annotation continues, off-ramp endpoint:

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

How a MatrixTrade casefile becomes a evidence filing:

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

Boundaries on every MatrixTrade casefile, never crossed:

• Boundary on MatrixTrade, seed phrases are off-limits.
• Boundary on MatrixTrade, remote logins are off-limits.
• Boundary on MatrixTrade, upfront cash retainers are off-limits.
• Boundary on MatrixTrade, guaranteed-recovery promises are off-limits.
• Boundary on MatrixTrade, unsolicited outbound contact is off-limits.