Feature Request: Immutable namestorage

[xloem]

I'd like to be able to mark a namestorage key as immutable, such that neither I nor anybody else can change it again, under any conditions; all transactions which change it are invalid.

[Skerberus]

Well only the owner of the name can change the corresponding namestorage so if you own the name you and only you have right to change it. Can you give a scenario where this is needed? Whenever the namestorage is changed you get a security api call where you can deny the change if you want that. The namestoragehistory moreover allows to see even older values, so you could just revert to that point if you like :). http://qora.co.in:9090/index/namestoragehistory.html

[xloem]

If your private key is compromised, an attacker could change the data. Especially in subtle ways you may not notice.

[Skerberus]

Ok yes, but if you e.g. sell a name and the former owner locked all the keys in the namestorage the new owner would be angry probably, currently the namestorage gets erased if you sell a name. Moreover with this behaviour no one will be able to change a given key, so if you do that to a profile key by mistake you will have problems too. I currently see too many downfalls to implement that behaviour, especially because data is never really lost, so you can always get everything back with the namestoragehistory.

[xloem]

How about this?

• UI makes it very clear that locking a key is a permanent action, and both the UI and API make it difficult to do.
• Names with locked/immutable keys may never be sold. (or with more work, interface makes it clear to purchaser what has been locked, and locked keys are not erased)

I'm concerned about phishing and co-opting where most people would never think to check the namestorage, and then be misled. For example, if somebody publicizes a public key, you wouldn't want somebody else to be able to create the same document with the same url with a different public key in it.