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
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <runesvend@gmail.com>) id 1UF9RK-0004xv-Ug
for bitcoin-development@lists.sourceforge.net;
Mon, 11 Mar 2013 20:35:22 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.176 as permitted sender)
client-ip=209.85.212.176; envelope-from=runesvend@gmail.com;
helo=mail-wi0-f176.google.com;
Received: from mail-wi0-f176.google.com ([209.85.212.176])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UF9RG-0007ru-Vb
for bitcoin-development@lists.sourceforge.net;
Mon, 11 Mar 2013 20:35:22 +0000
Received: by mail-wi0-f176.google.com with SMTP id hm14so1306737wib.15
for <bitcoin-development@lists.sourceforge.net>;
Mon, 11 Mar 2013 13:35:12 -0700 (PDT)
X-Received: by 10.194.7.196 with SMTP id l4mr21978708wja.28.1363034112799;
Mon, 11 Mar 2013 13:35:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.44.132 with HTTP; Mon, 11 Mar 2013 13:34:52 -0700 (PDT)
In-Reply-To: <201303111935.55767.luke@dashjr.org>
References: <1363030071-26731-1-git-send-email-runesvend@gmail.com>
<201303111935.55767.luke@dashjr.org>
From: =?ISO-8859-1?Q?Rune_Kj=E6r_Svendsen?= <runesvend@gmail.com>
Date: Mon, 11 Mar 2013 21:34:52 +0100
Message-ID: <CAH2=CKyyjPoOTHS6bE7TBCE4UGXf+qnGv0xq-eSHg-iXMH2Rqw@mail.gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=047d7b5d45761c384204d7ac1c24
X-Spam-Score: -0.6 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(runesvend[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UF9RG-0007ru-Vb
Subject: Re: [Bitcoin-development] [PATCH] Change recommended fee to 0.001
BTC
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: Mon, 11 Mar 2013 20:35:23 -0000
--047d7b5d45761c384204d7ac1c24
Content-Type: text/plain; charset=ISO-8859-1
Ok. I'll fork on Github. Looking at the source, and some Qt documentation,
it should be doable to do string substitution for both the value and the
unit.
The question is if we should define a new value, that we use solely to
display in this text, or if we should use MIN_TX_FEE or MIN_RELAY_TX_FEE in
some way. What are the dev's thoughts?
I'd like to get some more dev opinions on whether this should even be done
before I go ahead and write the code.
/Rune
On Mon, Mar 11, 2013 at 8:35 PM, Luke-Jr <luke@dashjr.org> wrote:
> On Monday, March 11, 2013 7:27:51 PM Rune K. Svendsen wrote:
> > From: "Rune K. Svendsen" <runesvend@gmail.com>
> >
> > On the Main tab in the Options dialog, it previously said a minimum
> > fee of 0.01 is recommended. This amounts to about $0.50 at today's
> > price. Change this to 0.001 to be more sensible. We could even go
> > lower, perhaps.
>
> Please use GitHub pull requests (or at least publish a git repository)
> rather
> than mailing patches..
>
> I'd suggest two commits for this:
> 1. Move the recommended fee outside the translatable string (bonus points
> to
> format it using the user's preferred unit)
> 2. Change the recommended fee in one place
>
> Whether the recommended fee *should* be changed or not, I have no opinion
> on.
> Eligius uses a lower minimum fee, but I believe most pools/miners will
> treat
> anything under 0.01 BTC as if it were no fee at all...
>
> Luke
>
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7b5d45761c384204d7ac1c24
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Ok. I'll fork on Github. Looking at the source, and so=
me Qt documentation, it should be doable to do string substitution for both=
the value and the unit.<div><br></div><div>The question is if we should de=
fine a new value, that we use solely to display in this text, or if we shou=
ld use=A0MIN_TX_FEE or MIN_RELAY_TX_FEE in some way. What are the dev's=
thoughts?<div style>
<br></div><div style>I'd like to get some more dev opinions on whether =
this should even be done before I go ahead and write the code.</div></div><=
div class=3D"gmail_extra"><br clear=3D"all"><div><div style><font color=3D"=
#500050">/Rune</font></div>
</div><br><div class=3D"gmail_quote">On Mon, Mar 11, 2013 at 8:35 PM, Luke-=
Jr <span dir=3D"ltr"><<a href=3D"mailto:luke@dashjr.org" target=3D"_blan=
k">luke@dashjr.org</a>></span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">On Monday, March 11, 2013 7:27:51 PM Rune K. Svendsen wro=
te:<br>
> From: "Rune K. Svendsen" <<a href=3D"mailto:runesvend@gma=
il.com">runesvend@gmail.com</a>><br>
><br>
> On the Main tab in the Options dialog, it previously said a minimum<br=
>
> fee of 0.01 is recommended. This amounts to about $0.50 at today's=
<br>
> price. Change this to 0.001 to be more sensible. We could even go<br>
> lower, perhaps.<br>
<br>
</div>Please use GitHub pull requests (or at least publish a git repository=
) rather<br>
than mailing patches..<br>
<br>
I'd suggest two commits for this:<br>
1. Move the recommended fee outside the translatable string (bonus points t=
o<br>
format it using the user's preferred unit)<br>
2. Change the recommended fee in one place<br>
<br>
Whether the recommended fee *should* be changed or not, I have no opinion o=
n.<br>
Eligius uses a lower minimum fee, but I believe most pools/miners will trea=
t<br>
anything under 0.01 BTC as if it were no fee at all...<br>
<br>
Luke<br>
<br>
---------------------------------------------------------------------------=
---<br>
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester<br>
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" =
in the<br>
endpoint security space. For insight on selecting the right partner to<br>
tackle endpoint security challenges, access the full report.<br>
<a href=3D"http://p.sf.net/sfu/symantec-dev2dev" target=3D"_blank">http://p=
.sf.net/sfu/symantec-dev2dev</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div></div>
--047d7b5d45761c384204d7ac1c24--
|
