📅 Original date posted:2011-12-16
🗒️ Summary of this message: A proposal to enable complete user@server.com handling in Bitcoin by extending the protocol for transactions to IP addresses and enabling DNS lookups.
📝 Original message:This is the first proposal I've seen regarding mapping something like
user at host that actually makes sense to me.
Bitcoin itself is decentralised by design, in my opinion it seems obvious
that it needs to continue to maintain this feature.
On Fri, Dec 16, 2011 at 8:59 AM, theymos <theymos at mm.st> wrote:
> Bitcoin already has code and a protocol for transactions to IP
> addresses. Why not reuse that for dynamic address lookup? Just a few
> changes are necessary to enable complete user at server.com handling:
> - Extend the protocol so that "reply" messages can be signed by a fixed
> public key
> - Extend "checkorder" messages so they can specify an account to
> send BTC to. Or standardize on how to put the account into the
> message field.
> - Enable DNS lookups for IP transactions. The DNS-only proposals could
> also be used here to avoid having to use the IP transaction protocol
> sometimes. The public key for signing "reply" messages can be gotten
> from TXT records. This will be safe with DNSSEC and Namecoin. With
> plain DNS Bitcoin could take a SSH-like approach and ask the user to
> verify the public key the first time it is used, remembering it later.
>
> DoS attacks are already handled by the IP transactions code: the same IP
> address is always given the same bitcoin address until it pays to that
> bitcoin address.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111216/f86f05de/attachment.html>;
Kyle Henderson [ARCHIVE] /
npub1ws…fv6kh
2023-06-07 02:43:22
in reply to nevent1q…dthg
Author Public Key
npub1ws7kd2knmz65wpdh2xsymr85e2lkuqhktkvfq0a8h9snt9td96ksafv6khPublished at
2023-06-07 02:43:22Event JSON
{
"id": "bf194681ee7635b7830cfe793b989dba911d67db02a076cbcb6c1c15aa47de1f",
"pubkey": "743d66aad3d8b54705b751a04d8cf4cabf6e02f65d98903fa7b96135956d2ead",
"created_at": 1686105802,
"kind": 1,
"tags": [
[
"e",
"247922e9146ee6b54a634fc05ad7a489892c01debcd0510d008be95a47f6db80",
"",
"root"
],
[
"e",
"d87b9faeaff06476a48eba6322673a993da3bd76f90e91641119a7034cc077f5",
"",
"reply"
],
[
"p",
"c86b2a2e41d61aaf7ab7198ba65cf5a35c015f3117a71eaba5e19bb537b20051"
]
],
"content": "📅 Original date posted:2011-12-16\n🗒️ Summary of this message: A proposal to enable complete user@server.com handling in Bitcoin by extending the protocol for transactions to IP addresses and enabling DNS lookups.\n📝 Original message:This is the first proposal I've seen regarding mapping something like\nuser at host that actually makes sense to me.\n\nBitcoin itself is decentralised by design, in my opinion it seems obvious\nthat it needs to continue to maintain this feature.\n\n\nOn Fri, Dec 16, 2011 at 8:59 AM, theymos \u003ctheymos at mm.st\u003e wrote:\n\n\u003e Bitcoin already has code and a protocol for transactions to IP\n\u003e addresses. Why not reuse that for dynamic address lookup? Just a few\n\u003e changes are necessary to enable complete user at server.com handling:\n\u003e - Extend the protocol so that \"reply\" messages can be signed by a fixed\n\u003e public key\n\u003e - Extend \"checkorder\" messages so they can specify an account to\n\u003e send BTC to. Or standardize on how to put the account into the\n\u003e message field.\n\u003e - Enable DNS lookups for IP transactions. The DNS-only proposals could\n\u003e also be used here to avoid having to use the IP transaction protocol\n\u003e sometimes. The public key for signing \"reply\" messages can be gotten\n\u003e from TXT records. This will be safe with DNSSEC and Namecoin. With\n\u003e plain DNS Bitcoin could take a SSH-like approach and ask the user to\n\u003e verify the public key the first time it is used, remembering it later.\n\u003e\n\u003e DoS attacks are already handled by the IP transactions code: the same IP\n\u003e address is always given the same bitcoin address until it pays to that\n\u003e bitcoin address.\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111216/f86f05de/attachment.html\u003e",
"sig": "a4fdfa42a3273efbd8153bf5291a86369dae76121a51ae9ff3fb55a4f8780855d47589494eeecc644a0846c4170011104078844100dbcaaddfaca0d1cdf83349"
}