I have a group of dev's that have been working on a service for over a year and just not getting around to growing the integration. I've reached out Evan about the service and haven't heard back. People say they want it easy but then they actually have to make the steps to become easy. From my first day in crypto I HATED public keys. They will always be the #1 turnoff for anyone. As soon as they see them, they turn off and move on. Its just too confusing. Before the great INET, we had BBS's and those BBSs had telephone numbers. No one remembered the number but they remembered the name. DNS for websites did the same and buying a domain name was might more expensive than today. Now take that and apply it to crypto. (Did I mention I HATE public keys.)
I think the idea in itself is great, but there are a couple of things I don't know how to weight them
- So far I was completely happy when someone sends me his/her pubkey and I put a name on it in my wallet. But others my want more of course
- It's centralized. As long as it's not widely used (with servers and mirrors for MY domain instead of one instance having it all) that's a weak point. Servers get DDOSed/hacked/whatnot and you'd have a lot of problems.
- It kind of contradicts the "anonymous" part of Dash
But again, don't get me wrong, I think it's a cool idea. Make it P2P (e.g. each wallet serves it's own names or something like this. Or delegate it to Masternodes) and it would be perfect.