Wallet trace — what the Professor maps:

• Deposit transaction hashes from the claimant wallet to the RubyFinance platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

The Professor’s off-ramp note:

• RubyFinance casefiles end at a centralised exchange — Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for RubyFinance is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for RubyFinance — the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the RubyFinance casefile.

The Professor’s recovery note for RubyFinance:

1. Submission triage — RubyFinance casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace — RubyFinance deposit and forwarding wallets captured.
3. Endpoint identification — RubyFinance off-ramp wallet named.
4. Filing — RubyFinance packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow — RubyFinance stays on file until a documented next step is reached.

Chains and off-ramps the Professor follows:

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

What the Professor will never do — by policy:

• What the Professor will not do on RubyFinance — ask for a seed phrase.
• What the Professor will not do on RubyFinance — request remote-access logins.
• What the Professor will not do on RubyFinance — demand cash up front.
• What the Professor will not do on RubyFinance — promise a guarantee.
• What the Professor will not do on RubyFinance — call you out of the blue.