Author: Rick Wesson 2011-12-16 16:03:28
Published on: 2011-12-16T16:03:28+00:00
In an email thread, Pieter Wuille proposed using URLs as address identifiers, optionally suffixed with a bitcoin address for authentication. For example, his "address" could be either "sipa.be/pw.btc" or "sipa.be/pw.btc$14TYdpodQQDKVgvUUcpaMzjJwhQ4KYsipa", where "https://" is an implicit default. Initiating a payment to either of these would result in a GET of https://sipa.be/pw.btc and when a transaction is constructed, it is POSTed back to that URL. He suggested that if they could agree on reasonable hardcoded mapping, pw at sipa.be could just be a shorthand for either of these, though vulnerable to proofing. In response to this proposal, Rick Falkvinge suggested looking at DANE and reviewing their work on hardening certificate (x.509) infrastructure as any URI scheme will still leverage DNS and inherit any base issues with TXT records. He also advised reviewing some of the work done in the IETF which has a long history in addressing many of the issues being considered. Finally, he recommended that if they cannot reach nearly the same level of sophistication as the bitcoin protocols, then they should rethink their scheme, as the proposals in this thread are neither clear nor elegant.
Updated on: 2023-06-04T21:56:18.799200+00:00