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-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WxTJu-0006Yp-Vz for bitcoin-development@lists.sourceforge.net; Thu, 19 Jun 2014 03:47:27 +0000 X-ACL-Warn: Received: from quidecco.de ([81.169.136.15]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WxTJs-0004aQ-5q for bitcoin-development@lists.sourceforge.net; Thu, 19 Jun 2014 03:47:26 +0000 Received: from localhost (localhost [127.0.0.1]) by quidecco.de (Postfix) with SMTP id 71C3ADFD05D; Thu, 19 Jun 2014 05:47:17 +0200 (CEST) From: Isidor Zeuner To: =?ISO-8859-1?Q?Jorge_Tim=F3n?= Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; format=flowed References: In-Reply-To: Message-Id: <20140619034717.71C3ADFD05D@quidecco.de> Date: Thu, 19 Jun 2014 05:47:17 +0200 (CEST) X-Spam-Score: -0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1WxTJs-0004aQ-5q Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] 0 confirmation txs using replace-by-fee and game theory 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: Thu, 19 Jun 2014 03:47:27 -0000 quote: [...] > On 4/24/14, Chris Pacia wrote: > > It would work but it's an ugly hack IMO. What do people do if they don't > > have extra to pay when making a purchase? I have 200 mbtc and want to buy a > > 200 mbtc phone but I can't because I need 400 mbtc. Sucks for me. > > > > I would much prefer the hassle of a green address notary than always having > > to make sure I have double what I need to make a purchase. > > This scheme wouldn't be mandatory. You can still wait for > confirmations or rely somehow on existing trust instead if that's > better for you on that situation. > Considering hotel or car rental payments where the credit card processor reserves a higher amount in order to cover risks, it doesn't seem like anything new or particularly inconvenient that a payment system may require a larger amount than the final price being available. Which brings us to the question: Is it an important characteristic in a payment system that it is capable of quickly spending your last penny? Best regards, Isidor