From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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?= Date: Mon, 11 Mar 2013 21:34:52 +0100 Message-ID: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 wrote: > On Monday, March 11, 2013 7:27:51 PM Rune K. Svendsen wrote: > > From: "Rune K. Svendsen" > > > > 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
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.

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?

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 class=3D"gmail_extra">
/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 wro= te:
> 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 t= o
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 o= n.
Eligius uses a lower minimum fee, but I believe most pools/miners will trea= t
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-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--047d7b5d45761c384204d7ac1c24--