Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YIFKg-0001nA-9J for bitcoin-development@lists.sourceforge.net; Mon, 02 Feb 2015 11:38:22 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.178 as permitted sender) client-ip=74.125.82.178; envelope-from=laanwj@gmail.com; helo=mail-we0-f178.google.com; Received: from mail-we0-f178.google.com ([74.125.82.178]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YIFKe-0003Jd-Dz for bitcoin-development@lists.sourceforge.net; Mon, 02 Feb 2015 11:38:22 +0000 Received: by mail-we0-f178.google.com with SMTP id k48so38447312wev.9 for ; Mon, 02 Feb 2015 03:38:14 -0800 (PST) X-Received: by 10.194.80.193 with SMTP id t1mr42369820wjx.8.1422877094328; Mon, 02 Feb 2015 03:38:14 -0800 (PST) Received: from amethyst.lan (e107003.upc-e.chello.nl. [213.93.107.3]) by mx.google.com with ESMTPSA id dj4sm27471651wjc.13.2015.02.02.03.38.13 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Feb 2015 03:38:13 -0800 (PST) Date: Mon, 2 Feb 2015 12:38:12 +0100 (CET) From: Wladimir To: Levin Keller In-Reply-To: Message-ID: References: User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-1829059981-1422877093=:21504" X-Spam-Score: 1.2 (+) 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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 2.8 MALFORMED_FREEMAIL Bad headers on message from free email service 0.0 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1YIFKe-0003Jd-Dz Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Export format for xpub 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: Mon, 02 Feb 2015 11:38:22 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323328-1829059981-1422877093=:21504 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Mon, 2 Feb 2015, Levin Keller wrote: > Hello everyone, > I think this is my first email to this mailinglist so I will shortly introduce myself: > > I am Levin and the CEO of Coyno (www.coyno.com). Based in Berlin, mathematician. Bitcoiner since 2011. > > And now the reason for this email: Andreas (Schildbach) just released a new update of his wallet. It now provides an export functionality for the m/0' key in order to run read only copies > on other devices. We already support the format on our website. Of course we would love for this to become standard. I also updated the Wiki article for Andreas' > Wallet: https://en.bitcoin.it/wiki/Bitcoin_Wallet Yes, standardizing on a format could be useful. > How do you like it? How does this format get standard? Shall I try to get a pull request to BIP32 passed? Just administrative trivia: this would be a new BIP, and not an amandment to BIP32. Excluding small language errors and clarifications in examples, BIPs are not changed after the fact. Wladimir --8323328-1829059981-1422877093=:21504--