Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1W1aGr-0003Tb-NW for bitcoin-development@lists.sourceforge.net; Fri, 10 Jan 2014 11:29:01 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of zikula.org designates 74.125.82.48 as permitted sender) client-ip=74.125.82.48; envelope-from=drak@zikula.org; helo=mail-wg0-f48.google.com; Received: from mail-wg0-f48.google.com ([74.125.82.48]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1W1aGq-0004zL-Sr for bitcoin-development@lists.sourceforge.net; Fri, 10 Jan 2014 11:29:01 +0000 Received: by mail-wg0-f48.google.com with SMTP id x13so3881217wgg.15 for ; Fri, 10 Jan 2014 03:28:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=D/66s+0U2OKOlK8Pm7BVAvfdeti0F80Xgxo9aljDEDU=; b=MAOLhZnhMzSN1wMsuc1ICYaNhhSMwiT+Wx7nCJh7TGtNy8W56Y74iWWybuTLZjI+XQ 5oZb3YAAHi83QGs9mqcVleQL10Ax+PC467kdrliJxzUNPIyITKPET31dUWoXROGYgXFg 7ZPMy/W4MQB6Gfu5SJK/z5mJNvqwO8Mwo0OCthf+aSu97eKvnaK9AcWxl9LS/jlgm1Bm xAW6A1X7rRFRkQ8bm9CkZGw6nDIYxX4G46AxhyKjXCOpnhv+gDjINqjwHk0kOUdJLKH5 jK+BPh3an+aizk5hK8WfR1DmO5BDpNYPB2FZQ+lDyW4c1zbrMbSw0ol9r88OOuvDr6iM 7prg== X-Gm-Message-State: ALoCoQkJZe/vfo2nA3/gWFpWKl1MUBcAVJsZUQMe1qJKDrlpq8Ingqm+bToFHqNOYAjdtxSAQYrv X-Received: by 10.180.97.39 with SMTP id dx7mr2242068wib.10.1389353334658; Fri, 10 Jan 2014 03:28:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.30.8 with HTTP; Fri, 10 Jan 2014 03:28:33 -0800 (PST) In-Reply-To: <20140110102037.GB25749@savin> References: <20140106120338.GA14918@savin> <20140110102037.GB25749@savin> From: Drak Date: Fri, 10 Jan 2014 11:28:33 +0000 Message-ID: To: Peter Todd Content-Type: multipart/alternative; boundary=f46d04428f22faf17f04ef9c07e9 X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1W1aGq-0004zL-Sr Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Stealth Addresses X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jan 2014 11:29:01 -0000 --f46d04428f22faf17f04ef9c07e9 Content-Type: text/plain; charset=UTF-8 On 10 January 2014 10:20, Peter Todd wrote: > Oh, sorry, I forgot to mention it in my first write-up but you can > easily make stealth addresses include a second pubkey for the purpose of > the communication that either isn't used in the scriptPubKey at all, or > is part of a n-of-m multisig. (n>=2) Interestingly that also means you > can give a third-party that key and out-source the effort of scanning > the blockchain for you. That seems pretty exciting to me. What is the chance of this becoming a BIP? Drak --f46d04428f22faf17f04ef9c07e9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On 1= 0 January 2014 10:20, Peter Todd <pete@petertodd.org> wrote= :
Oh, sorry, I forgot t= o mention it in my first write-up but you can
easily make stealth addresses include a second pubkey for the purpose of the communication that either isn't used in the scriptPubKey at all, or=
is part of a n-of-m multisig. (n>=3D2) Interestingly that also means you=
can give a third-party that key and out-source the effort of scanning
the blockchain for you.

That seems pretty e= xciting to me. What is the chance of this becoming a BIP?

Drak=C2=A0
--f46d04428f22faf17f04ef9c07e9--