{"type":"rich","version":"1.0","author_name":"npub12rkw0jajmsck4uwdtksdvtswrlkypusfryjzera7m4fhqta6jhdsz3aqxc","author_url":"https://nostr.ae/npub12rkw0jajmsck4uwdtksdvtswrlkypusfryjzera7m4fhqta6jhdsz3aqxc","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-01-10\n📝 Original message:On 10 January 2014 10:20, Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\n\u003e Oh, sorry, I forgot to mention it in my first write-up but you can\n\u003e easily make stealth addresses include a second pubkey for the purpose of\n\u003e the communication that either isn't used in the scriptPubKey at all, or\n\u003e is part of a n-of-m multisig. (n\u003e=2) Interestingly that also means you\n\u003e can give a third-party that key and out-source the effort of scanning\n\u003e the blockchain for you.\n\n\nThat seems pretty exciting to me. What is the chance of this becoming a BIP?\n\nDrak\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140110/24259da9/attachment.html\u003e"}