I hosted and event at our farm and had about 20 folks come out to discuss legal and techie issues around bitcoin. We found it really difficult to exchange bitcoins and constructed an idea on a better way to get a bitcoin wallet identifier to one of our friends.
The first solution would be to use DNS TXT records to put a bitcoin address into, much as SPF records did for adding anti-spam capabilities. The second option is to use NAPTR records but it offers less capability over TXT. My third option is to develop an internet-draft for a WA (wallet-address) record and offer it to the DNS community.
The TXT records could be something like BTC=1; <address> The first label defines the curency and its version, the second is the address. For the label I'm considering _btc.<name> where name would need to be either ASCII-7 or a internationalized punycode label for UTF-8 names.
I'd really like to associate the address with a label under a domain so that sendtoaddress could leverage syntax much like sendto firstname.lastname@example.org
which would cause the client rpc code to lookup the TXT record from _btc.rick.wesson.us and insert the resuting address into the pwalletMain->SendMoneyToBitcoinAddress (line 511 in rpc.h)
My three work items are:
o simple internet-draft describing the WA (wallet address) record
o patches for bitcoind and bitcoinJ
I believe that by leveraging wallet addresses in the DNS will allow more folks to feel comfortable by sending money to email@example.com
rather than 1GCVXLfF1TcpnnDLJRHk845NZhuJWQTnUD
Looking for advise, mostly regarding how to get a patch accepted into the mainline.