{"type":"rich","version":"1.0","author_name":"npub1ep4j5tjp6cd2774hrx96vh845dwqzhe3z7n3a2a9uxdm2dajqpgscm3rel","author_url":"https://nostr.ae/npub1ep4j5tjp6cd2774hrx96vh845dwqzhe3z7n3a2a9uxdm2dajqpgscm3rel","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-12-15\n🗒️ Summary of this message: Bitcoin developers discuss reusing code for IP transactions to enable dynamic address lookup and mitigate security flaws, with minimal protocol extension.\n📝 Original message:This is maybe the best idea. I added it:\nhttps://en.bitcoin.it/wiki/BIP_0015#IP_Transactions\n\nThings I like about this:\n- IP transactions are useful, but have a security flaw. This mitigates their security problems.\n- The code for IP transactions is already in Satoshi client. If other clients want to add IP transactions, then it can be done with minimal fuss/bloat.\nI feel that for any protocol extension, less is more. The less code \nneeded, the better the extension. Not always but generally we want to \navoid bitcoin protocol bloat which *will* happen far in the future. The \nonly way to mitigate how spaghettified the standard will be in the \nfuture, is by careful cautious planning now.\n\n- We can have a proxy node running 24/7 for us, serving our public keys in lieu of us.\n\n\n\n________________________________\n From: theymos \u003ctheymos at mm.st\u003e\nTo: bitcoin-development at lists.sourceforge.net \nSent: Thursday, December 15, 2011 7:59 PM\nSubject: Re: [Bitcoin-development] [BIP 15] Aliases\n \nBitcoin 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.\n\n------------------------------------------------------------------------------\n10 Tips for Better Server Consolidation\nServer virtualization is being driven by many needs.  \nBut none more important than the need to reduce IT complexity \nwhile improving strategic productivity.  Learn More! \nhttp://www.accelacomm.com/jaw/sdnl/114/51507609/\n_______________________________________________\nBitcoin-development mailing list\nBitcoin-development at lists.sourceforge.net\nhttps://lists.sourceforge.net/lists/listinfo/bitcoin-development\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111215/ea93e7ce/attachment.html\u003e"}