From: "Rune Kjær Svendsen" <runesvend@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] [PATCH] Change recommended fee to 0.001 BTC
Date: Mon, 11 Mar 2013 21:34:52 +0100 [thread overview]
Message-ID: <CAH2=CKyyjPoOTHS6bE7TBCE4UGXf+qnGv0xq-eSHg-iXMH2Rqw@mail.gmail.com> (raw)
In-Reply-To: <201303111935.55767.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 2914 bytes --]
next prev parent reply other threads:[~2013-03-11 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 19:27 Rune K. Svendsen
2013-03-11 19:35 ` Luke-Jr
2013-03-11 20:34 ` Rune Kjær Svendsen [this message]
2013-03-11 20:45 ` Gregory Maxwell
[not found] ` <201303112046.51263.luke@dashjr.org>
2013-03-11 21:17 ` Rune Kjær Svendsen
2013-03-11 21:29 ` Luke-Jr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH2=CKyyjPoOTHS6bE7TBCE4UGXf+qnGv0xq-eSHg-iXMH2Rqw@mail.gmail.com' \
--to=runesvend@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox