Reading the wallets, Range Capltd casefile:

• Deposit confirmations from the claimant to Range Capltd’s receiving wallet at range-capltd.com.
• 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.

The annotation continues, off-ramp endpoint:

• On the Range Capltd casefile, the off-ramp endpoint resolves to a centralised exchange, Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for Range Capltd is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the Range Capltd casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, Range Capltd escalates to IC3, state AG, and civil-discovery overlay.

How a Range Capltd casefile becomes a evidence filing:

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

What the Professor will never do, by policy:

• Boundary on Range Capltd, seed phrases are off-limits.
• Boundary on Range Capltd, remote logins are off-limits.
• Boundary on Range Capltd, upfront cash retainers are off-limits.
• Boundary on Range Capltd, guaranteed-recovery promises are off-limits.
• Boundary on Range Capltd, unsolicited outbound contact is off-limits.