Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wd4xy-0002eT-Ud for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 21:44:30 +0000 X-ACL-Warn: Received: from mail-ee0-f46.google.com ([74.125.83.46]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wd4xx-0002iq-21 for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 21:44:30 +0000 Received: by mail-ee0-f46.google.com with SMTP id t10so1208833eei.19 for ; Wed, 23 Apr 2014 14:44:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DuaRggwU9OtApai1wCqLqEnrorIbfAw2lV3xQm0pOY4=; b=gPMBwqC2gc7c/0A/5WQCy17ttNdeGiLgoMzksDzJM6ibkfczICep/IaolEukgBKzS0 pmJ+FMaR40sKiLmrb81de0TWDifm4usHrcgtMgKb9U9VetAVS95CnhA9i3MNW1/jmvN6 ywAMZo1oBd6rWdph3Ow7vszosndDNwHWvyasyrGR0u7FS0w54gKag0LM28302O7HtRss OiMRNNU1rPIN7ItRRXUsFmy+nyRCyGJQHydrTiNv338osWKiciQoDda6Yh8UaKODbQn8 7lKfQlWU+6BPdR+vmI0rvb5VjboIhAbqmEdEoflhJfYq3M5fX01oyIJAmC5kA3nL4BBF Xowg== X-Gm-Message-State: ALoCoQlW628aYSQg/6fI8DyCrqEKmq70ZGnn1BQLNJTF5cXGo95s7258/tEgX+JPoAdgdVnQyUuB X-Received: by 10.14.216.2 with SMTP id f2mr19156633eep.83.1398289462470; Wed, 23 Apr 2014 14:44:22 -0700 (PDT) Received: from tetra.site (nat-0-15.lam.cz. [80.92.242.254]) by mx.google.com with ESMTPSA id o4sm9802103eef.20.2014.04.23.14.44.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Apr 2014 14:44:21 -0700 (PDT) Message-ID: <53583434.5080601@gk2.sk> Date: Wed, 23 Apr 2014 23:44:20 +0200 From: Pavol Rusnak User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 CC: Bitcoin Development References: <53582B52.70205@gk2.sk> <201404232118.58316.luke@dashjr.org> <535831BC.1090707@gk2.sk> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 1.2 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.2 MISSING_HEADERS Missing To: header X-Headers-End: 1Wd4xx-0002iq-21 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 21:44:31 -0000 On 04/23/2014 11:42 PM, Pieter Wuille wrote: > In that case, maybe it makes sense to define another purpose id > without accounts as well already. > > I believe many simple wallets will find multiple subwallets too > burdening for the user experience, or not worth the technical > complexity. Right. See my previous email where I describe hypothetical creation of BIP65 and BIP66 which the exact thing you describe. -- Best Regards / S pozdravom, Pavol Rusnak