From mboxrd@z Thu Jan 1 00:00:00 1970 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 1We2rj-0007xv-SJ for bitcoin-development@lists.sourceforge.net; Sat, 26 Apr 2014 13:42:03 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.171 as permitted sender) client-ip=209.85.213.171; envelope-from=pieter.wuille@gmail.com; helo=mail-ig0-f171.google.com; Received: from mail-ig0-f171.google.com ([209.85.213.171]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1We2ri-00015H-2Y for bitcoin-development@lists.sourceforge.net; Sat, 26 Apr 2014 13:42:03 +0000 Received: by mail-ig0-f171.google.com with SMTP id c1so3197001igq.10 for ; Sat, 26 Apr 2014 06:41:56 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.43.26.206 with SMTP id rn14mr12814870icb.13.1398519716748; Sat, 26 Apr 2014 06:41:56 -0700 (PDT) Received: by 10.50.127.243 with HTTP; Sat, 26 Apr 2014 06:41:56 -0700 (PDT) In-Reply-To: <535BA597.70708@gk2.sk> References: <1398437607.23028.110362141.03111A2A@webmail.messagingengine.com> <535B8C43.8030502@gmx.de> <535BA597.70708@gk2.sk> Date: Sat, 26 Apr 2014 15:41:56 +0200 Message-ID: From: Pieter Wuille To: Pavol Rusnak Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) 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 (pieter.wuille[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 X-Headers-End: 1We2ri-00015H-2Y Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] BIP32 "wallet structure" in use? Remove it? 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 Apr 2014 13:42:04 -0000 On Sat, Apr 26, 2014 at 2:24 PM, Pavol Rusnak wrote: > On 04/26/2014 12:48 PM, Tier Nolan wrote: >> Maybe the solution is to have a defined way to import an unknown wallet? > > That is nonsense. There is no way how to import the wallet if you don't > know its structure. I agree. Especially when multiple chains are combined (multisig) for P2SH usage, defining things like a gap limit becomes impossible without knowing some metadata. However, perhaps it is possible to define something like "BIP44 import-compatible", meaning that the application doesn't actually support all of BIP44 features, but does guarantee not losing any funds when imported? Similar things could be done for other purpose types. -- Pieter