📅 Original date posted:2011-12-15
🗒️ Summary of this message: Bitcoin's existing protocol for transactions to IP addresses can be modified to enable complete user handling at server.com through a few changes, including extending the protocol for signed "reply" messages and enabling DNS lookups for IP transactions. DoS attacks are already handled.
📝 Original message: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.
theymos [ARCHIVE] /
npub10v…mper0
2023-06-07 02:43:16
in reply to nevent1q…hq9f
Author Public Key
npub10vt6y7m6shn8hfuj83zjlwcga4fky38kv73qz6xlcvtj4q7fjt0sqmper0Seen on
wss://relay.nostr.bandPublished at
2023-06-07 02:43:16Event JSON
{
"id": "41c86be30f0bb996c4b6dfc7cb794c59e5d419db8ee5aa2b5ac373bcacd60815",
"pubkey": "7b17a27b7a85e67ba7923c452fbb08ed536244f667a20168dfc3172a83c992df",
"created_at": 1686105796,
"kind": 1,
"tags": [
[
"e",
"247922e9146ee6b54a634fc05ad7a489892c01debcd0510d008be95a47f6db80",
"",
"root"
],
[
"e",
"b439d8d056fd14a22fe16320a7c0ad11e0ad4711c0efadc3ba0121695ecff836",
"",
"reply"
],
[
"p",
"498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84"
]
],
"content": "📅 Original date posted:2011-12-15\n🗒️ Summary of this message: Bitcoin's existing protocol for transactions to IP addresses can be modified to enable complete user handling at server.com through a few changes, including extending the protocol for signed \"reply\" messages and enabling DNS lookups for IP transactions. DoS attacks are already handled.\n📝 Original message:Bitcoin already has code and a protocol for transactions to IP\naddresses. Why not reuse that for dynamic address lookup? Just a few\nchanges are necessary to enable complete user at server.com handling:\n- Extend the protocol so that \"reply\" messages can be signed by a fixed\n public key\n- Extend \"checkorder\" messages so they can specify an account to\n send BTC to. Or standardize on how to put the account into the\n message field.\n- Enable DNS lookups for IP transactions. The DNS-only proposals could\n also be used here to avoid having to use the IP transaction protocol\n sometimes. The public key for signing \"reply\" messages can be gotten\n from TXT records. This will be safe with DNSSEC and Namecoin. With\n plain DNS Bitcoin could take a SSH-like approach and ask the user to\n verify the public key the first time it is used, remembering it later.\n\nDoS attacks are already handled by the IP transactions code: the same IP\naddress is always given the same bitcoin address until it pays to that\nbitcoin address.",
"sig": "796fe65af5dea8185d25e68dd6049a2c1bd8fd33dbbac969f1a50716cf0f26ef2d82005b9683366413915a615457c10d4cbafc832c1a32aba07a0525ddd45ed9"
}