From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Uh16e-00086i-2x for bitcoin-development@lists.sourceforge.net; Mon, 27 May 2013 17:21:12 +0000 X-ACL-Warn: Received: from nm9-vm6.bullet.mail.ne1.yahoo.com ([98.138.91.102]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Uh16b-0000vs-KS for bitcoin-development@lists.sourceforge.net; Mon, 27 May 2013 17:21:12 +0000 Received: from [98.138.226.180] by nm9.bullet.mail.ne1.yahoo.com with NNFMP; 27 May 2013 17:21:04 -0000 Received: from [98.138.89.192] by tm15.bullet.mail.ne1.yahoo.com with NNFMP; 27 May 2013 17:21:04 -0000 Received: from [127.0.0.1] by omp1050.mail.ne1.yahoo.com with NNFMP; 27 May 2013 17:21:04 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 325221.63152.bm@omp1050.mail.ne1.yahoo.com Received: (qmail 64269 invoked by uid 60001); 27 May 2013 17:21:04 -0000 X-YMail-OSG: AM6G_v0VM1keq_Q.VKOhD3t87.ZmZg2TSai2tLr7RMUnbqn p_gRUcaJl.aRSzZiYBDImFvW7TScjXUHGyAe1MQ6.YhA.jD_OxOaAIDFJ9EO GTK3DLd.RB.gAbXfeqzM9uzwxURsTqLWp3UveqLYtCSg6wsytwog5KUvNYL. MbGAxgit7eo5gEX8.Sh.t2O6pYn1j2VtNx7csO11anohLPLvlvs_nrIC.wQq KFMhcYqN20xxuTSrMym9Zk0EjpL1KaM6ZbhnmDc41FY7rKE9GVOqp_SpOqw7 YEFCRIgITpwdYWR9xahT3NCH7rYNdTN1oB3mZX_owY3DFfa5YtlsjR.EZibF NaeP45Q1wa.6HqmxOtpeYM_o3cQ.WbaBsydZ6WVdKKpziAblo4q9hgl9z8T1 ofNC5jJLC.aace0R7NA9d_dr6Xk0wFhZjFz3rDEeZ0KNL8zwJwWMHCnWBhS5 4RYYA_zy46sWYNolkcmDgM8JnB4bghYR9H7RJ_4_aD9Ecw3jq.Vv73CNJOKB 8EXR7KvhPnXrTFToWoTlI3MhHZ7bGezI8lQcNTg-- Received: from [217.171.129.78] by web121706.mail.ne1.yahoo.com via HTTP; Mon, 27 May 2013 10:21:04 PDT X-Rocket-MIMEInfo: 002.001, WWVhaCwgSSB0cmllZCBpbXBsZW1lbnRpbmcgaXQgYmFzZWQgb24gdGhlIGRvY3VtZW50IHRoZXJlIGFuZCB0aGUgY29kZSB0aGF0IGlzIGF2YWlsYWJsZSBpbiBzaXBhJ3MgcmVwbyBvbiBHaXRIdWIgYnV0IGl0J3Mgbm90IGVub3VnaC4gSSdtIHdhaXRpbmcgdW50aWwgdGhlcmUgaXMgYW4gaW1wbGVtZW50YXRpb24gb2YgdGhpcyBjb25jZXB0IGJlZm9yZSBtb3Zpbmcgb24gaXQuCgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCiBGcm9tOiBNaWNoYWVsIEdyb25hZ2VyIDxncm9uYWdlckBjZXABMAEBAQE- X-Mailer: YahooMailWebService/0.8.144.546 References: <51A32A30.8040504@ceptacle.com> <51A35B2C.7060802@ceptacle.com> <51A36207.90307@ceptacle.com> Message-ID: <1369675264.58806.YahooMailNeo@web121706.mail.ne1.yahoo.com> Date: Mon, 27 May 2013 10:21:04 -0700 (PDT) From: Amir Taaki To: "bitcoin-development@lists.sourceforge.net" In-Reply-To: <51A36207.90307@ceptacle.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-730330825-979606815-1369675264=:58806" X-Spam-Score: -0.2 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [98.138.91.102 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (zgenjix[at]yahoo.com) -1.1 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Uh16b-0000vs-KS Subject: Re: [Bitcoin-development] BIP0032 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Amir Taaki List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 17:21:12 -0000 ---730330825-979606815-1369675264=:58806 Content-Type: text/plain; charset=us-ascii Yeah, I tried implementing it based on the document there and the code that is available in sipa's repo on GitHub but it's not enough. I'm waiting until there is an implementation of this concept before moving on it. ________________________________ From: Michael Gronager To: bitcoin-development@lists.sourceforge.net Sent: Monday, May 27, 2013 2:39 PM Subject: Re: [Bitcoin-development] BIP0032 Which again means that the statement regarding Audits through the Master Public key, M, is wrong - only incoming and outgoing transaction of _publicly_ derived wallets will be part of the audit... Privately derived wallets cannot be obtained, though you could, without loss of security, share also the addition points from privately derived wallets: (m/i')*G, but there is no concept of a single public master key. == Audits: M In case an auditor needs full access to the list of incoming and outgoing payments, one can share the master public extended key. This will allow the auditor to see all transactions from and to the wallet, in all accounts, but not a single secret key. == ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development ---730330825-979606815-1369675264=:58806 Content-Type: text/html; charset=us-ascii
Yeah, I tried implementing it based on the document there and the code that is available in sipa's repo on GitHub but it's not enough. I'm waiting until there is an implementation of this concept before moving on it.

From: Michael Gronager <gronager@ceptacle.com>
To: bitcoin-development@lists.sourceforge.net
Sent: Monday, May 27, 2013 2:39 PM
Subject: Re: [Bitcoin-development] BIP0032

Which again means that the statement regarding Audits through the Master
Public key, M, is wrong - only incoming and outgoing transaction of
_publicly_ derived wallets will be part of the audit... Privately
derived wallets cannot be obtained, though you could, without loss of
security, share also the addition points from privately derived wallets:
(m/i')*G, but there is no concept of a single public master key.

==
Audits: M
In case an auditor needs full access to the list of incoming and
outgoing payments, one can share the master public extended key. This
will allow the auditor to see all transactions from and to the wallet,
in all accounts, but not a single secret key.
==



------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


---730330825-979606815-1369675264=:58806--