Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wd4no-0006RJ-9v for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 21:34:00 +0000 X-ACL-Warn: Received: from mail-ee0-f48.google.com ([74.125.83.48]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wd4nl-0007AN-Mx for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 21:34:00 +0000 Received: by mail-ee0-f48.google.com with SMTP id b57so1189292eek.35 for ; Wed, 23 Apr 2014 14:33:51 -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=zlhQ+rbzEV6h29phTz3g+6xJGgSyricolBBdFUWJWb4=; b=bSEUtcVChdWPCWoppr/FnX+7Xpk5/lbzd/+BYCCQ44yFCoh1Y5OCOO5XaYwo+z/VMh xCHLkHqSqEWi7/Wv4dZqVJ2dIIximW+Y+RDpxGnAIeoHikSgsLKW+0jaZlzAPyWYfozD tS7+9zQGK5D+03PXfZeEoJiYJsm4ZRVdPRVEaqCGm+kpUENK5NVZDNVxR7yGPE5CCD6l YVBUdlijngZIaBYgH5fbdXi1M56G4iD8wE4EOr9zkKfUmoBTVIdsYC/M85XU9rTLPGB0 eIipeVBISWEzILB1L97qHf06Ldg/J6Nh/od8R3rXEp03ak6YjMaEwrF3Kox02so3uK0b ziOw== X-Gm-Message-State: ALoCoQmMAZNZPLBsFplbN8gQ7V+m2i1zp443sIIOKhv/8h6DjGsxrk3Cr39WSPE+Ywu3TZ9YDZdc X-Received: by 10.15.10.3 with SMTP id f3mr65196073eet.1.1398288831283; Wed, 23 Apr 2014 14:33:51 -0700 (PDT) Received: from tetra.site (nat-0-15.lam.cz. [80.92.242.254]) by mx.google.com with ESMTPSA id e42sm9724647eev.32.2014.04.23.14.33.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Apr 2014 14:33:49 -0700 (PDT) Message-ID: <535831BC.1090707@gk2.sk> Date: Wed, 23 Apr 2014 23:33:48 +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> 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: 1Wd4nl-0007AN-Mx 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:34:00 -0000 On 04/23/2014 11:22 PM, Gregory Maxwell wrote: > Hopefully it would be clarified as only a MUST NOT do so silently... > "I have funds split across two wallets and it WONT LET ME SPEND THEM" > sounds like a terrible user experience. :) That is a subjective matter. To me it makes PERFECT SENSE that funds across accounts NEVER MIX. One can still send funds from one account to another and then perform another spend. That's what I consider a consistent and thus GOOD user experience. What's the purpose of Accounts if wallet mixes coins among them anyway? I know it's not good to use classic bank accounts as analogy, but that's exactly how they work. Or have you every done ONE transaction from two bank accounts simultaneously? -- Best Regards / S pozdravom, Pavol Rusnak