@accessor.eth The definition of cold storage hasn’t changed, what has changed is that people want to share cold wallets publicly and prove ownership of cold wallets using hot wallets.
Another way of explaining of what I’m (and many others) are trying to accomplish is:
- Protect my NFT collection (including ENS name) in cold storage
- Share my collection with people by simply providing my ENS name
- Identify in Web3 as my ENS name without putting my cold storage assets at risk
As @Premm.eth points out, 1 and 2 are possible, 3 is not. Secondary registries (like delegate.cash) popping up is evidence of demand for this use case. Doesn’t ENS want to be the registry?
What if, as an example, we carved off an exception for a specific subdomain like delegate, and delegate.yourname.eth always resolved to the Parent’s address instead of the address in the address field. Then I could point the address field of delegate to my hot wallet so it could set my Primary name.
Is this a viable solution?