I was looking at the wiki entry for this and noticed that your description of DNSSEC is incorrect. It is an internet standard and is widely deployed in the root (.), many TLDs, ccTLDs and second leverl domains.
Also understand when the IETF or ICANN adopts new (we worked on DNSSEC no less than 10 years) standard the horizon is at least 20 years. Nothing and I really mean nothing is adopted in mass over shorter time scales. I also am largely in favor of using secured zones to publish TXT records to digital currencies. I've been thinking mainly about TXT using the following format for bitcoin. _btc.<lhs>.<rhs> you can look up the following record _btc.rick.wesson.us (from r...@wesson.us) which yealds ; <<>> DiG 9.6-ESV-R4-P3 <<>> _btc.rick.wesson.us txt ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45136 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;_btc.rick.wesson.us. IN TXT ;; ANSWER SECTION: _btc.rick.wesson.us. 299 IN TXT "BTC=1\; 1GCVXLfF1TcpnnDLJRHk845NZhuJWQTnUD" ;; Query time: 147 msec while this isn't a secured zone, any leverage of DNSSEC would require the application to have direct hooks into the stub-resolver, rather than just leveraging the OS's implementation. just some food for thought... -rick 2011/12/14 Jorge Timón <timon.elvi...@gmail.com>: > What if we specify "bitcoin" to make it easier for software (maybe the > browser, a plugin for the browser, the bitcoin client analyzing the > clipboard...) to easily detect that you expect a bitcoin address when > going to url? > If puted in the bitcoin client, the "bitcoin://" is optional (? and > can also be replaced by http ?) since from the context you already > expect an address or an url that will give you the address. > > In the browser: > > bitcoin://address > bitcoin://rest_of_url > > In the bitcoin client: > > address > rest_of_url > bitcoin://address > bitcoin://rest_of_url > http://rest_of_url ?? > > Maybe in the bitcoin client you can put any site and the client > downloads the web to look for occurrences of "bitcoin://" (? or just > valid addresses ?) in it. It caches and shows them to you to decide > what to do with each one. > I have used other programs (jdownloader) that read the clipboard > looking for patterns in links and is very convenient. > > Maybe then parameters for the client can be added to this. > > bitcoin://address?amount=10.53 > bitcoin://rest_of_url?amount=10.53&green_address=r > bitcoin://rest_of_url?amount=10.53&green_address=r&green_address_list=address1,address2,address3 > > Whatever the community have planned for bitcoin URIs. > > ------------------------------------------------------------------------------ > Cloud Computing - Latest Buzzword or a Glimpse of the Future? > This paper surveys cloud computing today: What are the benefits? > Why are businesses embracing it? What are its payoffs and pitfalls? > http://www.accelacomm.com/jaw/sdnl/114/51425149/ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development ------------------------------------------------------------------------------ Cloud Computing - Latest Buzzword or a Glimpse of the Future? This paper surveys cloud computing today: What are the benefits? Why are businesses embracing it? What are its payoffs and pitfalls? http://www.accelacomm.com/jaw/sdnl/114/51425149/ _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
