1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
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 <andreas@petersson.at>) 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 <bitcoin-development@lists.sourceforge.net>
X-PHP-Originating-Script: 0:func.inc
MIME-Version: 1.0
Date: Fri, 25 Oct 2013 14:02:35 +0200
From: Andreas Petersson <andreas@petersson.at>
In-Reply-To: <20131025070708.GA5760@savin>
References: <20131024143043.GA12658@savin>
<CANEZrP100Lg_1LcFMKx1yWrGTSFb5GZmLmXNbZjPGaiEgOeuwA@mail.gmail.com>
<20131024144358.GA17142@savin>
<CANEZrP1TfM+wYbGjUk3+8JJZs6cKZXdb57xGMc=hDr9dQjMMZA@mail.gmail.com>
<20131024145447.GA19949@savin>
<CABsx9T0T0v=HnRRr6BLKNQOFMBJWrhF4G4SOCJ9DidGJBB8Eow@mail.gmail.com>
<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: <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: 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
|
