From the marginalia — the deposit pathway:

• Deposit transaction hashes from the claimant wallet to the RKFS 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.

From the lectern — off-ramp identification:

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

Pathway to recovery — what happens after the trail is mapped:

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

What the on-chain reading covers:

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

What the Professor will never do — by policy:

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