The annotation reads, wallet trace:

• Deposit confirmations from the claimant to BATTLE TRADE’s receiving wallet at battletrade.co.
• Forwarding-wallet pathway documented hop-by-hop with chain of custody hashes.
• Cross-chain bridge transactions where the operator routed value out of the deposit chain.
• Mixer or coin-join interactions, where applicable.
• Final off-ramp at a centralised exchange, the compliance counterparty named in the recovery filing.

Off-ramp summary, BATTLE TRADE casefile:

• On the BATTLE TRADE casefile, the off-ramp endpoint resolves to a centralised exchange, Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for BATTLE TRADE is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the BATTLE TRADE casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, BATTLE TRADE escalates to IC3, state AG, and civil-discovery overlay.

How a BATTLE TRADE casefile becomes a evidence filing:

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

What we read in a BATTLE TRADE casefile:

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