From mboxrd@z Thu Jan 1 00:00:00 1970 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 1VZgNS-0007yf-3r for bitcoin-development@lists.sourceforge.net; Fri, 25 Oct 2013 12:20:30 +0000 X-ACL-Warn: Received: from petersson.at ([213.239.210.117]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1VZgNQ-00074A-OH for bitcoin-development@lists.sourceforge.net; Fri, 25 Oct 2013 12:20:30 +0000 Received: by petersson.at (Postfix, from userid 33) id 590D56701C8; Fri, 25 Oct 2013 14:02:35 +0200 (CEST) To: Bitcoin Dev X-PHP-Originating-Script: 0:func.inc MIME-Version: 1.0 Date: Fri, 25 Oct 2013 14:02:35 +0200 From: Andreas Petersson In-Reply-To: <20131025070708.GA5760@savin> References: <20131024143043.GA12658@savin> <20131024144358.GA17142@savin> <20131024145447.GA19949@savin> <20131025070708.GA5760@savin> Message-ID: <91968c56640bf7647325728f490b9257@localhost> X-Sender: andreas@petersson.at User-Agent: RoundCube Webmail/0.2.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.4 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1VZgNQ-00074A-OH Subject: Re: [Bitcoin-development] Making fee estimation better 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: Fri, 25 Oct 2013 12:20:30 -0000 =0D > Worth thinking about the whole ecosystem of wallets involved; they all=0D > have to handle double-spends gracefully to make tx replacement of any=0D > kind user friendly. We should try to give people a heads up that this i= s=0D > coming soon if that's your thinking.=0D =0D If there is a situation where wallets are supposed to constantly monitor=0D the tx propagation and recreate their transactions with different fees,=0D this would make a lot of usecases inconvenient.=0D half-offline bluetooth transactions, users with unstable connections,=0D battery power lost, etc, etc. - and last but not least power concerns on=0D hardware wallets on the bitcoincard (tx signing drains a significant amou= nt=0D of power and should therefore only be done once)=0D =0D -Andreas