The Professor’s off-ramp note:

• Off-ramp endpoint for FxRally resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• FxRally’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for FxRally is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the FxRally off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

The Professor’s recovery note for FxRally:

1. First read on FxRally, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on FxRally, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for FxRally is named to a centralised exchange wallet.
4. Packet filing on FxRally, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with FxRally until a documented outcome or escalation step is on file.

What the casefile records, chains and counterparties:

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