On-chain reading, wallet flow for Acuity Trade Fx:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for Acuity Trade Fx.
• Forwarding wallets on the deposit chain, each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint, the centralised exchange deposit address holding the compliance lever.

How a Acuity Trade Fx casefile becomes a evidence filing:

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

What the casefile records, chains and counterparties:

• Chains tracked on Acuity Trade Fx, 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 Acuity Trade Fx, named exchange counterparties with public compliance contacts.
• Filings supported on Acuity Trade Fx, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.