Reading the wallets, Capital GatewayCG casefile:

• Claimant-to-platform deposit transactions on the deposit chain used by Capital GatewayCG.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet, the named centralised-exchange endpoint.

Off-ramp map, where the funds left the chain:

• Capital GatewayCG off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The Capital GatewayCG off-ramp address is matched to known compliance feeds, the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for Capital GatewayCG, the packet meets the off-ramp’s published compliance standard.
• When the Capital GatewayCG off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

How a Capital GatewayCG casefile becomes a evidence filing:

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

Boundaries on every Capital GatewayCG casefile, never crossed:

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