The Register · tokenized DHR
What a tokenized DHR holder owns
2 tokens issued by 2 programs track Danaher. They share a ticker and little else. 2 are on file; each row below links the file with the issuer’s own words.
What the holder owns
Every version on file (2) are notes or swaps that pay like the share and carry no rights in it: xStocks, rTokens. None gives the holder the Danaher share itself, and none carries SIPC protection in the wallet.
Who may hold it
No version on file is offered to US persons.
Who can freeze it
In 1 of the 2 programs with a readable contract, one private key can freeze, pause, or claw back holders’ tokens, or grant that power: xStocks.
Every version, side by side
| Version | What the holder has | Control | ||||
|---|---|---|---|---|---|---|
| Token | Program | Owns | Who may hold | Exit | Freeze key held by | Market cap |
| DHRX | xStocks | Third-party synthetic | Not offered to US persons | Redeem with the issuer in its window | A single key | $251K |
| RDHR | rTokens | Third-party synthetic | Not offered to US persons | Redeem with the issuer in its window | A power exists; its holder was not read | $158 |
Market cap is CoinGecko’s figure on 2026-09-24, for the token itself, not the share it tracks. “Freeze key held by” names the weakest key that can freeze, pause, or claw back a holder, or grant that power, read from the chain.
What the difference means
- Third-party synthetic
- A note or swap that pays like the security and carries no rights in it. xStocks, rTokens.