Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wd38W-00012X-Dq for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 19:47:16 +0000 X-ACL-Warn: Received: from mail-ve0-f174.google.com ([209.85.128.174]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wd38U-00017F-Re for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 19:47:16 +0000 Received: by mail-ve0-f174.google.com with SMTP id oz11so1702698veb.19 for ; Wed, 23 Apr 2014 12:47:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=528M3g8CN9tPiWQ58r1+tL9LoHPcwVX8D7JyVjx6c/c=; b=L541kXWBqrYIVq9BusXq4dYG+Hg2exGwhoAJcaFxxugA9zOl4pYvuYEjKfvjq76gGv 3NjMkIkiasU6ne2z5/nvSf/S7rgrvcvCqMiKmMRXWi6hf3a3zhc2MAvdcH+MscFFJi5N liJXl31nTrTg4bNrH+AuWp/LaWTx7AfxUJGO94d7uwJuXo+3y8Nc6oSDh2tebEnbEeum WRxatSQjSmo4gy+RmzqCf9d/2ePHePLPdUeTCM27zfO5Bcn5totfgY/niBouABQ4UKPe L0p2L9QI2Z22t/G3re8F5s3psnYSsRmJbTkIogzezp2o5PcX4mhQiUPdEh+RMrWXRvgH OJ4w== X-Gm-Message-State: ALoCoQn/0j/TFRiIMK2PGoNAC9gXgi+gV2XIECA386eoCrvoD/dJulXEdSSRUd+gF4u31Mtbdjqt X-Received: by 10.220.101.3 with SMTP id a3mr2103819vco.31.1398282429318; Wed, 23 Apr 2014 12:47:09 -0700 (PDT) MIME-Version: 1.0 Sender: marek@palatinus.cz Received: by 10.58.234.68 with HTTP; Wed, 23 Apr 2014 12:46:39 -0700 (PDT) In-Reply-To: <474624AD-9374-46A8-98E1-863EC290252D@bitsofproof.com> References: <53344FF8.7030204@gk2.sk> <53580A73.9070208@gk2.sk> <474624AD-9374-46A8-98E1-863EC290252D@bitsofproof.com> From: slush Date: Wed, 23 Apr 2014 21:46:39 +0200 X-Google-Sender-Auth: FL2yksMNt1rdSxMGIaTBbucl92U Message-ID: To: Tamas Blummer Content-Type: multipart/alternative; boundary=047d7b3a8d6a7ee3a504f7baff98 X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (slush[at]centrum.cz) 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1Wd38U-00017F-Re Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] New BIP32 structure 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: Wed, 23 Apr 2014 19:47:16 -0000 --047d7b3a8d6a7ee3a504f7baff98 Content-Type: text/plain; charset=ISO-8859-1 We do not want BIP64 to be incompatible with BIP32 in any way. BIP64 is just set of some recommendations for wallet developers how to browse bip32 tree. Modifying serialization format would break the compatibility. However we have our solution for storing wallet birth time, which is out of scope of BIP64, but we'll communicate it as soon as we'll write down that idea to some more specific format. Marek On Wed, Apr 23, 2014 at 9:36 PM, Tamas Blummer wrote: > Pieter suggested in IRC couple of months ago to append key birth to key > serialization in xprv....@unixtime format. > > What about picking this idea up in BIP64? It would greatly help the > importing client. > > Regards, > > Tamas Blummer > http://bitsofproof.com > > > --047d7b3a8d6a7ee3a504f7baff98 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
We do not want BIP64 to be incompatible with BIP32 in any = way. BIP64 is just set of some recommendations for wallet developers how to= browse bip32 tree.

Modifying serialization format would= break the compatibility.

However we have our solution for storing wallet birth t= ime, which is out of scope of BIP64, but we'll communicate it as soon a= s we'll write down that idea to some more specific format.

Marek 


On Wed, Apr 23, 2014 at 9:36 PM, Tamas Blummer <tamas@bitsofproof.com> wrote:
Pieter s= uggested in IRC couple of months ago to append key birth to key serializati= on in xprv….@unixtime format.

What about picking this idea up in BIP64? It would greatly h= elp the importing client.

Regards,
Tamas Blummer
http://bitsofproof.com



--047d7b3a8d6a7ee3a504f7baff98--