Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <jouke@bitonic.nl>) id 1UX93U-0008W9-Lw for bitcoin-development@lists.sourceforge.net; Tue, 30 Apr 2013 11:49:08 +0000 X-ACL-Warn: Received: from entix.nl ([178.22.57.40] helo=mail.entix.nl) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1UX93Q-0006t8-UF for bitcoin-development@lists.sourceforge.net; Tue, 30 Apr 2013 11:49:08 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.entix.nl (Postfix) with ESMTP id 6FB4014C0C8 for <bitcoin-development@lists.sourceforge.net>; Tue, 30 Apr 2013 13:32:55 +0200 (CEST) Received: from mail.entix.nl ([127.0.0.1]) by localhost (entix.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Y7ld+qTNirc for <bitcoin-development@lists.sourceforge.net>; Tue, 30 Apr 2013 13:32:55 +0200 (CEST) Received: from [192.168.1.139] (535608E7.cm-6-7a.dynamic.ziggo.nl [83.86.8.231]) by mail.entix.nl (Postfix) with ESMTPSA id F048414C050 for <bitcoin-development@lists.sourceforge.net>; Tue, 30 Apr 2013 13:32:54 +0200 (CEST) Message-ID: <517FABE6.8020205@bitonic.nl> Date: Tue, 30 Apr 2013 13:32:54 +0200 From: Jouke Hofman <jouke@bitonic.nl> User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <CABsx9T3egz=7YNOrgx7WsfSthLfN2gfE60YfPEv8096vyErBqg@mail.gmail.com> <20130428180304.GA30115@crunch> <CA+CODZEiWTrmFzrMi2Mi0qtH3dWO5UWx_j09iUwV2qm1O=3o0A@mail.gmail.com> <CANEZrP2JDc244xvR0ayM700Vy_h3G=aAUUgfxtOcxd0ZeB9b8g@mail.gmail.com> In-Reply-To: <CANEZrP2JDc244xvR0ayM700Vy_h3G=aAUUgfxtOcxd0ZeB9b8g@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1UX93Q-0006t8-UF Subject: Re: [Bitcoin-development] Cold Signing Payment Requests X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Tue, 30 Apr 2013 11:49:08 -0000 We do automatic refunds. When bitcoins arrive after an offer has expired (which happens quite often with webwallets that don't broadcast transactions immediately), we return all the bitcoins to a specified bitcoin-address. This happens a couple of times per day and can amount to a couple of hundred bitcoins per offer. On 04/30/2013 11:17 AM, Mike Hearn wrote: > If there are merchants that offer large, automatic refunds, it could be > an issue. I'm not sure how common that might be in reality. Steven or > Tony would know. Timo's protocol is an interesting solution, but again, > at this point the feature set for v1 is pretty much locked down.