Thanks for the link. That looks a bit more complicated than what we're doing, but definitely promising. Is there something in particular you wanted to point out?
Yes, I wanted to let you know that there is an ongoing discussion on aliases.
The proposal that I made might not be the final one, but it is already supported by Electrum.
In addition, the developer of Multibit is considering adding support for aliases into his client soon.
Another thing that I wanted to point out is that aliases can be signed.
This adds some level of protection against hijacking.
- an alias can be signed by a trusted authority. For example, your website could play that role, if you decide to host aliases.
The trusted authority should be reputable and not subject to hacking.
In addition, it may provide various services, such as verification of real-world identity, etc.
- an alias can be self-signed. This will protect only the users who have seen that alias previously, because their client will detect that the hijacked alias has a bad signature.
By the way, it would be awesome if electrum had support for querying the wallet list!
The current proposal does not allow a website to host aliases from other domains, but we could add this as an option in Electrum if your service is successful.
For addresses that belong to your domain (thewalletlist.com), all you need to do is a minor modification of your API :