The annotation reads, wallet trace:

• Deposit confirmations from the claimant to roitronix’s receiving wallet at roitronix.ltd.
• Forwarding-wallet pathway documented hop-by-hop with chain of custody hashes.
• Cross-chain bridge transactions where the operator routed value out of the deposit chain.
• Mixer or coin-join interactions, where applicable.
• Final off-ramp at a centralised exchange, the compliance counterparty named in the recovery filing.

Off-ramp map, where the funds left the chain:

• roitronix 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 roitronix is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for roitronix, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the roitronix casefile.

Recovery pathway, how this casefile moves toward filing:

1. Casefile triage on roitronix, the submission is read; a written assessment is delivered.
2. Forensic trace on roitronix, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the roitronix endpoint is named.
4. Recovery filing on roitronix, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of roitronix, the Professor follows the casefile until next-step documentation exists.

What the Professor will never do, by policy:

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