How about #Khal#, #Gavin.Andresen#, or #Bitinvestor# as pattern for the aliases? It would be easily recognized as a payment address and it can't be confused with an e-mail address.
This looks like a bit like hash tags. So, why not @Khal ?
Anyway, bitcoin can use the syntax it wants, namecoin will store data in it's own format (example: alias/Khal instead of #Khal)
* Make it independent of any coin (except Namecoin, obviously). Leave it up to the user to decide which coins to use and provide a secure data structure that any coin (existing or yet to be invented) can query to associate an e-mail address with a wallet address. While this feature isn't implemented by other coins it should still be possible to query Namecoin manually to list all the addresses for
gavin@acm.org so that the right one can be copied and pasted into the client.
This is the case.
Excellent! So what else do we need to make this work?
1. Add the Namecoin proposal to the existing BIP 15
2. Choose Namecoin as the solution among others
3. Finalize and validate the
Alias specification4. Explain how to create an alias