Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VaAmQ-0007ds-Dd for bitcoin-development@lists.sourceforge.net; Sat, 26 Oct 2013 20:48:18 +0000 X-ACL-Warn: Received: from mail-vb0-f47.google.com ([209.85.212.47]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VaAmP-0007tF-1N for bitcoin-development@lists.sourceforge.net; Sat, 26 Oct 2013 20:48:18 +0000 Received: by mail-vb0-f47.google.com with SMTP id m10so3556498vbh.34 for ; Sat, 26 Oct 2013 13:48:11 -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=gFDChL4iTVPGeREo70PVOpO4RugL1Q1AGZOWETv35xY=; b=kknWcaZ+5y+z1i1l0w+6J3uCXOl9HgnFqR4d1r00IR/XmUExHMXLFWmjY3Oq55xJT5 6oE7oeRiVMKYzAioPUvaewA7iBU9t/8nZMCvLrEjeK3IoTpjxHmlfQtYd4BhrGZfjqCl iIsUeL9jcV+98s7146ZBR1CDPrlxNU1kUgdXLfMAw+y876mD4Yx0+uBHnSj8J4ONqq2U RL8lWQGzZQDC9caVa4W38EWkbudir/2Dl2xs4OeMWmsyaCEs18GpLqfHDwwHakNBNthY BhUHHq3QbGAzimuKMybDcq/2zxJ++sVu2O54TVfhUHGN8J6jm1d30d1LDRLh/LqpdUez bilA== X-Gm-Message-State: ALoCoQlWrFZ8L+E19aKGI65dMJdPKMFAf9bEOZXSQbEu5R8pn5djrVRtE3Q59zl7U/sXYi32CyJH X-Received: by 10.58.19.195 with SMTP id h3mr3085vee.48.1382820491343; Sat, 26 Oct 2013 13:48:11 -0700 (PDT) MIME-Version: 1.0 Sender: marek@palatinus.cz Received: by 10.59.1.2 with HTTP; Sat, 26 Oct 2013 13:47:41 -0700 (PDT) In-Reply-To: <526BDEC2.2090709@gmx.de> References: <526BDEC2.2090709@gmx.de> From: slush Date: Sat, 26 Oct 2013 22:47:41 +0200 X-Google-Sender-Auth: Bo9GtXjn7xYqE_aBntuKGMreVy4 Message-ID: To: Thomas Voegtlin Content-Type: multipart/alternative; boundary=047d7b86c81e2cecf404e9aafc04 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 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: doubleclick.net] 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: 1VaAmP-0007tF-1N Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] Proposal to replace BIP0039 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: Sat, 26 Oct 2013 20:48:18 -0000 --047d7b86c81e2cecf404e9aafc04 Content-Type: text/plain; charset=ISO-8859-1 Hi Thomas, can you more elaborate on that "version" bits? What is exact meaning of it? I still think this is more an implementation problem. What stops Electrum to do the same algorithm for searching branches as it is now for used addresses? These "version bits" need to be covered by the specification as well, because if any client will use them differently (or won't use them at all), it will break cross-compatibility between clients, which was another goal of bip39. Marek On Sat, Oct 26, 2013 at 5:24 PM, Thomas Voegtlin wrote: > here is a simple implementation, with some ideas on how to format the > metadata: > https://en.bitcoin.it/wiki/Talk:BIP_0039 > > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --047d7b86c81e2cecf404e9aafc04 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Thomas,

can you more elaborate on th= at "version" bits? What is exact meaning of it? I still think thi= s is more an implementation problem. What stops Electrum to do the same alg= orithm for searching branches as it is now for used addresses?

These "version bits" need to be covered= by the specification as well, because if any client will use them differen= tly (or won't use them at all), it will break cross-compatibility betwe= en clients, which was another goal of bip39.

Marek




On Sat, O= ct 26, 2013 at 5:24 PM, Thomas Voegtlin <thomasv1@gmx.de> wrot= e:
here is a simple implementation, with some i= deas on how to format the
metadata:
http= s://en.bitcoin.it/wiki/Talk:BIP_0039


---------------------------------------------------------------------------= ---
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most fr= om
the latest Intel processors and coprocessors. See abstracts and register &g= t;
http://pubads.g.doubleclick.net/gam= pad/clk?id=3D60135991&iu=3D/4140/ostg.clktrk
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--047d7b86c81e2cecf404e9aafc04--