On-chain reading, wallet flow for MacroFxTrade:

• Deposit-side hashes from claimant wallets into MacroFxTrade’s receiving addresses.
• Operator forwarding wallets, deposit consolidation documented to chain of custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

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

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

Recovery pathway, how this casefile moves toward filing:

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

Reading-list, chains and exchanges in scope:

• Chains tracked on MacroFxTrade, Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on MacroFxTrade, named exchange counterparties with public compliance contacts.
• Filings supported on MacroFxTrade, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.