Each application has its own space, so Bitcoin will store its data in the "bitcoin" space.
I don't understand this. Why not one "cryptocoin" space that all coins can access? You could have BTC, NMC, and LTC addresses registered in your alias. When you want to send some NMC the Namecoin client uses the NMC address and when you want to send some BTC the Bitcoin client uses the BTC address.
Each coin can update his format separately and implement features when they want. I think it's more clear like that too.
- a secure way to get an address from an http request
Sorry, I don't understand. Please explain.
I've updated the BIP 15.
Here is a copy/paste :
You can put an url and a bitcoin address that will be used to sign the result. It means that a query to this url will return a bitcoin address and a signature. Bitcoin can then check (with the verify_message function) that the returned address has not been replaced by another one.
Did i missed some important use case ?
I'm under the impression that it's up to the user to decide what he wants to register under his alias: cryptocoin addresses, e-mail addresses, phone numbers, etc. If this is the case then it should be future proof.
Yes, applications and the community propose their formats/spaces and users decide what to put under their alias.
Great idea possibly. Still the issue of squatters possibly buying out well-known id's too.. not sure how well that'll go.
Yeah, if this takes off then we will end up with names similar to the usernames on Ebay. The only way to prevent squatting is to make it expensive to register a name, but then fewer people will use it.
Indeed, but before reaching ebay's popularity.... :p
Emails are interesting for that point, because it is segmented by domain names.
Maybe we could use a syntax like <name>@<group/location/what we want> ?