Wallet trace — what the Professor maps:

• Deposit confirmations from the claimant to Rangebits’s receiving wallet at rangebits.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:

• Off-ramp endpoint for Rangebits resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Rangebits’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Rangebits is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the Rangebits off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

How a Rangebits casefile becomes a regulator-ready filing:

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

What we read in a Rangebits casefile:

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

Lines we never cross — by published policy:

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