Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXYpP-00067r-SM for bitcoin-development@lists.sourceforge.net; Tue, 08 Apr 2014 16:24:51 +0000 X-ACL-Warn: Received: from mail-vc0-f170.google.com ([209.85.220.170]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WXYpO-0004zS-SV for bitcoin-development@lists.sourceforge.net; Tue, 08 Apr 2014 16:24:51 +0000 Received: by mail-vc0-f170.google.com with SMTP id hu19so1002777vcb.29 for ; Tue, 08 Apr 2014 09:24:45 -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=R/2aX0aOUR7lhglJUcnKioZDXT7ZgSwI9J/DKHciB4Y=; b=PpUSQYp1XHIaweJSRxxwrPNRzc1jJCMcR+o6iPgqZ9/Z+28tmCLY01j5sbgQjcR6ai afayiHmBxmL9B7qpXSqmnKPN8iddwhiiHsqTZ9Yi8jJDdZK0uvERRPgs3ghRwBf2ARi1 /EF19w+jUTCr0IuyLHxH3CSQYC4RrpPZRFPBIlNGyl1jLQdWf8PlxnaqQR+pkU1jn2VU BbZKfiHOOwpGakgLIh3ACPzTbyx5Kbsk9cxerSFWFt9j8kTjuXPSIVitvpFnZS+6qQkM 6K9FzUDWCQkCNi/bDE+hdXXHE+cCOTO6qn7ajDbInuJSkG+02oTMgvNDoDkHktRMMWYs 6XNQ== X-Gm-Message-State: ALoCoQn64GHmm61JRT5RpSALjVF3psCC9awOUHwcLM1mf7vjXPFWYie/3Gc93dL10QALR2V+eQbD X-Received: by 10.220.106.84 with SMTP id w20mr3967815vco.18.1396974285236; Tue, 08 Apr 2014 09:24:45 -0700 (PDT) MIME-Version: 1.0 Sender: marek@palatinus.cz Received: by 10.58.234.100 with HTTP; Tue, 8 Apr 2014 09:24:14 -0700 (PDT) In-Reply-To: References: <53344FF8.7030204@gk2.sk> From: slush Date: Tue, 8 Apr 2014 18:24:14 +0200 X-Google-Sender-Auth: QiN1ctjl5_-WEQ7g-xbNB44qq8s Message-ID: To: Andreas Schildbach Content-Type: multipart/alternative; boundary=047d7b3435c008421704f68a6c47 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: 1WXYpO-0004zS-SV Cc: "bitcoin-development@lists.sourceforge.net" 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: Tue, 08 Apr 2014 16:24:52 -0000 --047d7b3435c008421704f68a6c47 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Apr 8, 2014 at 5:58 PM, Andreas Schildbach wrote: > On 04/08/2014 05:46 PM, slush wrote: > > > It still doesn't mean that bitcoinj or Electrum cannot share the bare > > minimum of BIP XX. Of course if somebody will use Electrum for 2to3 > > transactions and then move wallet to client which does not offer such > > feature, it won't work. But I don't see that as a problem. > > There is no "bare minimum". Either you implement the "BIP" fully or not. > I didn't mean "Bare minimum of some spec", but "spec describing bare minimum", which is different. I'm sorry for confusion. Marek --047d7b3435c008421704f68a6c47 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Tue, Apr 8, 2014 at 5:58 PM, Andreas Schildbach <andreas@sc= hildbach.de> wrote:
On 04/08/2014 05:46 PM, slus= h wrote:

> It still doesn't mean that bitcoinj or Electrum cannot share the b= are
> minimum of BIP XX. Of course if somebody will use Electrum for 2to3 > transactions and then move wallet to client which does not offer such<= br> > feature, it won't work. But I don't see that as a problem.

There is no "bare minimum". Either you implement the "= BIP" fully or not.

I didn't me= an "Bare minimum of some spec", but "spec describing bare mi= nimum", which is different. I'm sorry for confusion.

Marek
--047d7b3435c008421704f68a6c47--