summaryrefslogtreecommitdiff
path: root/c3/db8998f0f05cec3498d4fd52fa3d2031e7dbdc
blob: 6c821df9367a0b9d47f3cbb802ff0e8044abb55d (plain)
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
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <drak@zikula.org>) id 1Vnns2-00048B-Hj
	for bitcoin-development@lists.sourceforge.net;
	Tue, 03 Dec 2013 11:10:26 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of zikula.org
	designates 74.125.82.53 as permitted sender)
	client-ip=74.125.82.53; envelope-from=drak@zikula.org;
	helo=mail-wg0-f53.google.com; 
Received: from mail-wg0-f53.google.com ([74.125.82.53])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Vnnrt-0003zs-Nn
	for bitcoin-development@lists.sourceforge.net;
	Tue, 03 Dec 2013 11:10:26 +0000
Received: by mail-wg0-f53.google.com with SMTP id k14so10842550wgh.20
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 03 Dec 2013 03:10:11 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type;
	bh=cswFkHXQDNMgb2kPDHqCZ4lKdy7vRXgrI6VEaFbaxJo=;
	b=ZwE4Ub7urSHR0OC+D0pTD0L1T20Ec6HPViYQNiKBPEmc83UkzslVdve3f44aqGak8G
	ZL0zJqFRla8DXXUcPQ3qAfUekO+VUiszN/rpq9gg0CvmteTuYOmmq1pkD6EFPCkXtYbE
	/Ab5uUVQhVwqwwXrAOa77gz6JIttaPhrAlrhF34eJL0wv+sCianfyRStnecaW72b9ImJ
	5mWqbTbO+/UFR5lYXDOXuUE4uCFm+4BEXcWHrH0qWUaQMh4yy83n78oviJFYAqqGyvcQ
	thJh6+Kt7GrxaPXh9Osxx2tjK+L96P1n21R1u76Wh9tksSnv8VJef6JjGP6a55chhhPo
	+DDQ==
X-Gm-Message-State: ALoCoQmZFpttc9gvGoL8RZlvUirdA7TIhJKgXkRwxP4uKVTh2N4rxeCsDftuxhN166dnR5YEZ4QI
X-Received: by 10.194.236.199 with SMTP id uw7mr6548376wjc.63.1386069011413;
	Tue, 03 Dec 2013 03:10:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.93.105 with HTTP; Tue, 3 Dec 2013 03:09:51 -0800 (PST)
In-Reply-To: <20131203110354.GA6513@tilt>
References: <CANEZrP3tGdFh6oG5fbX9JbU6sYbbex1cq=0tQB-0A4aDrdbXrQ@mail.gmail.com>
	<l7f97u$jdg$1@ger.gmane.org>
	<5E4597E4-C1C7-4536-8CF0-82EDD7715DAB@plan99.net>
	<l7fpbn$hf6$1@ger.gmane.org>
	<39921E12-B411-4430-9D56-04F53906B109@plan99.net>
	<CAGLkj4C9fyAX1CnB0oZH3BwLRQp6WOo9kLUqDhRUSA6y3LxYvg@mail.gmail.com>
	<CANEZrP1C=Hc-3f-rqQ+wYrPn-eUj52HjN+qRQdJMWvnP+dkK=Q@mail.gmail.com>
	<CAJHLa0P_uzEQ2OG2FTXyD2Zw4RzujNBxKbKD04CSS1sLNpLUUQ@mail.gmail.com>
	<CANEZrP2hf2853w9f4__Ji9v3eRRU0u6pEzPxAmFN+iH067gtnA@mail.gmail.com>
	<CABsx9T3NQDPL6=pz5BD5DsP0qh0x3LJOCj2H3yY5tzL2_DivGA@mail.gmail.com>
	<20131203110354.GA6513@tilt>
From: Drak <drak@zikula.org>
Date: Tue, 3 Dec 2013 11:09:51 +0000
Message-ID: <CANAnSg10KnY=oSM61onYjw5Fp==BwByEeoZUXWfzHqNFjsHYGA@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=089e01493e440f515204ec9f5717
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	-0.0 SPF_PASS               SPF: sender matches SPF record
	0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
	See
	http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
	for more information. [URIs: petertodd.org]
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1Vnnrt-0003zs-Nn
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Floating fees and SPV clients
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, 03 Dec 2013 11:10:26 -0000

--089e01493e440f515204ec9f5717
Content-Type: text/plain; charset=UTF-8

On 3 December 2013 11:03, Peter Todd <pete@petertodd.org> wrote:

> UI once both are implemented is to not show anything in the default
> case, and explain to the user why they have to pay extra in the unusual
> case where they are spending a whole bunch of dust.


Yes, that's the other problem with a merchant setting a fee - they have no
idea how large the transaction might be. If you spend a bunch of dust the
fee could be 2 or 3x the expected fee. Then you might get merchants
including higher fees by default to account for this. That means we end up
paying more per kb over time.

--089e01493e440f515204ec9f5717
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 3=
 December 2013 11:03, Peter Todd <span dir=3D"ltr">&lt;<a href=3D"mailto:pe=
te@petertodd.org" target=3D"_blank">pete@petertodd.org</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">

<div class=3D"im"><span style=3D"color:rgb(34,34,34)">UI once both are impl=
emented is to not show anything in the default</span><br></div>
case, and explain to the user why they have to pay extra in the unusual<br>
case where they are spending a whole bunch of dust.</blockquote><div><br></=
div><div>Yes, that&#39;s the other problem with a merchant setting a fee - =
they have no idea how large the transaction might be. If you spend a bunch =
of dust the fee could be 2 or 3x the expected fee. Then you might get merch=
ants including higher fees by default to account for this. That means we en=
d up paying more per kb over time.</div>

</div></div></div>

--089e01493e440f515204ec9f5717--