On-chain reading, wallet flow for SGB Finance:

• Initial deposit hashes to the SGB Finance receiving address at sgbfinancesa.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:

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

How a SGB Finance casefile becomes a evidence filing:

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