From the marginalia — the deposit pathway:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for ForexRuby.
• 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.

The annotation continues — off-ramp endpoint:

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

How a ForexRuby casefile becomes a regulator-ready filing:

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

Reading-list — chains and exchanges in scope:

• Chains in scope for ForexRuby — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for ForexRuby — named centralised exchanges with compliance leverage.
• Filings supported on ForexRuby — IC3, state AG, off-ramp desk, civil discovery as applicable.

Boundaries on every ForexRuby casefile — never crossed:

• ForexRuby policy — seed phrases are never requested.
• ForexRuby policy — remote-access logins are never requested.
• ForexRuby policy — no upfront cash retainer to scope.
• ForexRuby policy — no guaranteed-recovery language. None.
• ForexRuby policy — no unsolicited calls. The Professor responds in writing only.