From: Gmail <will.yager@gmail•com>
To: Peter Grigor <peter@grigor•ws>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Fee Formula Proposal
Date: Mon, 12 May 2014 20:46:24 -0500 [thread overview]
Message-ID: <D6A11BEA-1612-4A92-83BA-584C1F99E070@gmail.com> (raw)
In-Reply-To: <CAGpx8BVhQaO3+zeRgsMBgZa8-6L6+4k60tpQYOVBtFxVjoyBkw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 352 bytes --]
What about 0 confirmation inputs?
Mightn't this make tiny "spam" transactions unsafely inexpensive?
> On May 12, 2014, at 20:21, Peter Grigor <peter@grigor•ws> wrote:
>
>
> 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.
[-- Attachment #1.2: Type: text/html, Size: 951 bytes --]
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 1593 bytes --]
next prev parent reply other threads:[~2014-05-13 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 1:21 Peter Grigor
2014-05-13 1:46 ` Gmail [this message]
2014-05-13 10:02 ` Bernd Jendrissek
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=D6A11BEA-1612-4A92-83BA-584C1F99E070@gmail.com \
--to=will.yager@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=peter@grigor$(echo .)ws \
/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