Mmm, yea. But is RNS sovereign enough over just the usual domain names etc..., to justify any move/adoption from orgs at all?
If the value prop is "sovereign", you go all the way, no?
Login to reply
Replies (1)
I haven't looked too deep into the contract, but theoretically you can make a contract that doesn't allow any authority intervention not even to upgrade it. In that case I would count it as sovereign, you only pay rent.
However, the same orgs that might prefer RNS to MNS, might also just prefer ICANN to Blockchains..
I also don't hate living in a world where apps support both .mns.alt and .rsk.alt
MNS is primarily meant to work like phone numbers and be provisioned to users who never and would never pay for a domain... So if it also worked for orgs the way some orgs are happy with DIDs and Npubs, that's a bonus, but if they must use RNS, or even ENS, that's ok.