From: Bernd Jendrissek <bitcoin@bpj-code.co.za>
To: Peter Grigor <peter@grigor.ws>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin Fee Formula Proposal
Date: Tue, 13 May 2014 12:02:08 +0200 [thread overview]
Message-ID: <CAF7PVPpC5Qz9Ajy4kN1dRNSP7rRXxAQEHe1OvUkV_0E8mQsMfg@mail.gmail.com> (raw)
In-Reply-To: <CAGpx8BVhQaO3+zeRgsMBgZa8-6L6+4k60tpQYOVBtFxVjoyBkw@mail.gmail.com>
On Tue, May 13, 2014 at 3:21 AM, Peter Grigor <peter@grigor.ws> wrote:
> This was originally submitted to the bitcoin github issue manager. I'm
> re-posting here.
>
> I propose the transaction fee should be calculated from a percentage of the
> input amount divided by the confirmations of the input multiplied by the
> number of inputs.
For reference: https://github.com/bitcoin/bitcoin/issues/4171
I think the responses in the issue tracker already adequately address
why this doesn't belong in *Bit*coin. Your cure is worse than the
disease, IMHO.
prev parent reply other threads:[~2014-05-13 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 1:21 [Bitcoin-development] Bitcoin Fee Formula Proposal Peter Grigor
2014-05-13 1:46 ` Gmail
2014-05-13 10:02 ` Bernd Jendrissek [this message]
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=CAF7PVPpC5Qz9Ajy4kN1dRNSP7rRXxAQEHe1OvUkV_0E8mQsMfg@mail.gmail.com \
--to=bitcoin@bpj-code.co.za \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=peter@grigor.ws \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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