<div class="gmail_quote">This is the first proposal I've seen regarding mapping something like user@host that actually makes sense to me.<br>
<br>
Bitcoin itself is decentralised by design, in my opinion it seems obvious that it needs to continue to maintain this feature.<br><br><br>On Fri, Dec 16, 2011 at 8:59 AM, theymos <span dir="ltr"><<a href="mailto:theymos@mm.st">theymos@mm.st</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Bitcoin already has code and a protocol for transactions to IP<br>
addresses. Why not reuse that for dynamic address lookup? Just a few<br>
changes are necessary to enable complete <a href="mailto:user@server.com">user@server.com</a> handling:<br>
- Extend the protocol so that "reply" messages can be signed by a fixed<br>
public key<br>
- Extend "checkorder" messages so they can specify an account to<br>
send BTC to. Or standardize on how to put the account into the<br>
message field.<br>
- Enable DNS lookups for IP transactions. The DNS-only proposals could<br>
also be used here to avoid having to use the IP transaction protocol<br>
sometimes. The public key for signing "reply" messages can be gotten<br>
from TXT records. This will be safe with DNSSEC and Namecoin. With<br>
plain DNS Bitcoin could take a SSH-like approach and ask the user to<br>
verify the public key the first time it is used, remembering it later.<br>
<br>
DoS attacks are already handled by the IP transactions code: the same IP<br>
address is always given the same bitcoin address until it pays to that<br>
bitcoin address.<br>
<div class="im HOEnZb"><br></div></blockquote></div>