📅 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
Amir Taaki [ARCHIVE] /
npub1ep…m3rel
2023-06-07 02:46:25
in reply to nevent1q…9y0r
Author Public Key
npub1ep4j5tjp6cd2774hrx96vh845dwqzhe3z7n3a2a9uxdm2dajqpgscm3relPublished at
2023-06-07 02:46:25Event JSON
{
"id": "f74285bb4386e3aeea3d04d1736d0ede04ba5b1b2f9fee96f1c684e0814b6c25",
"pubkey": "c86b2a2e41d61aaf7ab7198ba65cf5a35c015f3117a71eaba5e19bb537b20051",
"created_at": 1686105985,
"kind": 1,
"tags": [
[
"e",
"f45e7ca88e6eb3dd1e645e8e3cbb476c5b24e8003cb71eebe205594bb2a4d152",
"",
"root"
],
[
"e",
"8406e765036935f7437cb9840a166f8677924d1522aeb351dff9e468bfe304df",
"",
"reply"
],
[
"p",
"857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4"
]
],
"content": "📅 Original date posted:2011-12-13\n🗒️ 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.\n📝 Original message:Maybe I wasn't clear enough in the document, but this is the intent with the HTTPS proposal.\n\ngenjix at foo.org\n\nContacts 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.\n\nI'll clarify it later. This is the relevant line:\n\nstring strRequestUrl = strDomain + \"/bitcoin-alias/?handle=\" + pszEncodedNick;\n\nBetween 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).\n\n\n----- Original Message -----\nFrom: Gavin Andresen \u003cgavinandresen at gmail.com\u003e\nTo: Jorge Timón \u003ctimon.elviejo at gmail.com\u003e\nCc: \"bitcoin-development at lists.sourceforge.net\" \u003cbitcoin-development at lists.sourceforge.net\u003e\nSent: Tuesday, December 13, 2011 1:06 PM\nSubject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases\n\nI agree with Mike Hearn and Christian Decker-- paying to\n'somebody at foo.com' should become, behind the scenes, a HTTPS query to\nhttps://foo.com/something. If you just want to (say) donate to\neff.org, then paying to '@eff.org' aught to work nicely.\n\nAnd if namecoin ever takes off you'll pay to 'somebody at foo.bit'.\n\nIt seems to me that if it was DNS-based, the address should be\nsomething like 'somebody.bitcoin.foo.com'. But I think it is unlikely\npeople will setup and run a custom DNS server just to support bitcoin\npayments.\n\n-- \n--\nGavin Andresen\n\n------------------------------------------------------------------------------\nSystems Optimization Self Assessment\nImprove efficiency and utilization of IT resources. Drive out cost and \nimprove service delivery. Take 5 minutes to use this Systems Optimization \nSelf Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/\n_______________________________________________\nBitcoin-development mailing list\nBitcoin-development at lists.sourceforge.net\nhttps://lists.sourceforge.net/lists/listinfo/bitcoin-development",
"sig": "332348b0fb24ee073306bcfa80f862b36fb9d0b058e32aa4265b2e9154af7cf402effc8548a4c4acbcb38820f8f0a7107ef1c7bc90e12649751857480c1f1894"
}