Amir Taaki [ARCHIVE] on Nostr: 📅 Original date posted:2011-12-13 🗒️ Summary of this message: The proposal ...
📅 Original date posted:2011-12-13
🗒️ Summary of this message: The proposal suggests using HTTPS for Bitcoin aliases, with the option for a server service, and clarifies the relevant line of code.
📝 Original message:Maybe I wasn't clear enough in the document, but this is the intent with the HTTPS proposal.
genjix at foo.org
Contacts https://foo.org/bitcoin-alias/?handle=genjix and the system responds with a bitcoin address. Whether the system gives you a new address from a pool of addresses, or contacts the merchant behind the scenes is implementation defined.
I'll clarify it later. This is the relevant line:
string strRequestUrl = strDomain + "/bitcoin-alias/?handle=" + pszEncodedNick;
Between HTTPS service and server service, I lean slightly towards HTTPS (automatic encrypted connection, CAs + all benefits of DNS). But still interested in arguments in favour of a server service (daemon answering queries).
----- Original Message -----
From: Gavin Andresen <gavinandresen at gmail.com>
To: Jorge Timón <timon.elviejo at gmail.com>
Cc: "bitcoin-development at lists.sourceforge.net" <bitcoin-development at lists.sourceforge.net>
Sent: Tuesday, December 13, 2011 1:06 PM
Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases
I agree with Mike Hearn and Christian Decker-- paying to
'somebody at foo.com' should become, behind the scenes, a HTTPS query to
https://foo.com/something. If you just want to (say) donate to
eff.org, then paying to '@eff.org' aught to work nicely.
And if namecoin ever takes off you'll pay to 'somebody at foo.bit'.
It seems to me that if it was DNS-based, the address should be
something like 'somebody.bitcoin.foo.com'. But I think it is unlikely
people will setup and run a custom DNS server just to support bitcoin
payments.
--
--
Gavin Andresen
------------------------------------------------------------------------------
Systems Optimization Self Assessment
Improve efficiency and utilization of IT resources. Drive out cost and
improve service delivery. Take 5 minutes to use this Systems Optimization
Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
🗒️ Summary of this message: The proposal suggests using HTTPS for Bitcoin aliases, with the option for a server service, and clarifies the relevant line of code.
📝 Original message:Maybe I wasn't clear enough in the document, but this is the intent with the HTTPS proposal.
genjix at foo.org
Contacts https://foo.org/bitcoin-alias/?handle=genjix and the system responds with a bitcoin address. Whether the system gives you a new address from a pool of addresses, or contacts the merchant behind the scenes is implementation defined.
I'll clarify it later. This is the relevant line:
string strRequestUrl = strDomain + "/bitcoin-alias/?handle=" + pszEncodedNick;
Between HTTPS service and server service, I lean slightly towards HTTPS (automatic encrypted connection, CAs + all benefits of DNS). But still interested in arguments in favour of a server service (daemon answering queries).
----- Original Message -----
From: Gavin Andresen <gavinandresen at gmail.com>
To: Jorge Timón <timon.elviejo at gmail.com>
Cc: "bitcoin-development at lists.sourceforge.net" <bitcoin-development at lists.sourceforge.net>
Sent: Tuesday, December 13, 2011 1:06 PM
Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases
I agree with Mike Hearn and Christian Decker-- paying to
'somebody at foo.com' should become, behind the scenes, a HTTPS query to
https://foo.com/something. If you just want to (say) donate to
eff.org, then paying to '@eff.org' aught to work nicely.
And if namecoin ever takes off you'll pay to 'somebody at foo.bit'.
It seems to me that if it was DNS-based, the address should be
something like 'somebody.bitcoin.foo.com'. But I think it is unlikely
people will setup and run a custom DNS server just to support bitcoin
payments.
--
--
Gavin Andresen
------------------------------------------------------------------------------
Systems Optimization Self Assessment
Improve efficiency and utilization of IT resources. Drive out cost and
improve service delivery. Take 5 minutes to use this Systems Optimization
Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development