From the marginalia — the deposit pathway:

• Initial deposit hashes to the RubyMarkets receiving address at rubymarkets.com.
• Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
• Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
• Obfuscation events through mixer contracts and privacy services.
• Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

Off-ramp reading — exchange counterparty for RubyMarkets:

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

How a RubyMarkets casefile becomes a regulator-ready filing:

1. Triage on RubyMarkets — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on RubyMarkets — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on RubyMarkets — off-ramp endpoint matched to a named exchange counterparty.
4. File the RubyMarkets packet — IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on RubyMarkets — the Professor stays on the casefile until a documented next step exists.

What the on-chain reading covers:

• Deposit-side chains in RubyMarkets casefiles — typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT) — with bridge crossings noted.
• Off-ramps named in RubyMarkets packets — centralised exchanges that accept regulator-grade compliance filings.
• Filing options on RubyMarkets — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

Lines the Professor will not cross:

• Hard line on RubyMarkets — no seed-phrase requests, period.
• Hard line on RubyMarkets — no remote logins requested.
• Hard line on RubyMarkets — no upfront cash retainer.
• Hard line on RubyMarkets — no guarantee language.
• Hard line on RubyMarkets — no unsolicited phone outreach.