From: Harald Schilly <harald.schilly@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
"bitcoin@lists.bitcoin-austria.at"
<bitcoin@lists.bitcoin-austria.at>
Subject: [Bitcoin-development] floating fees statistics
Date: Sat, 12 Jul 2014 23:05:36 +0200 [thread overview]
Message-ID: <CAGG4CB4kJUKYDH-gGqvyEh6A7d7ETkZrQeas1kyEjUzYaB65Yg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
Hi
I've looked into this new floating fees algorithm. What I've started
is an ipython notebook to gather data and look into some statistics.
Right now it's probably not so exciting because the rules aren't
active, but maybe someone is interested in this or wants to extend it
a bit.
notebook:
http://nbviewer.ipython.org/github/haraldschilly/bitcoin-floating-fee-statistics/blob/master/estimatefee.ipynb
source:
https://github.com/haraldschilly/bitcoin-floating-fee-statistics/
The probably most interesting graph is the one attached. It's the time
series of the estimated fees per confirmation level over the course of
4 hours. The vertical green lines indicate where new blocks have been
found.
Harald
[-- Attachment #2: index.png --]
[-- Type: image/png, Size: 18631 bytes --]
reply other threads:[~2014-07-12 21:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAGG4CB4kJUKYDH-gGqvyEh6A7d7ETkZrQeas1kyEjUzYaB65Yg@mail.gmail.com \
--to=harald.schilly@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=bitcoin@lists.bitcoin-austria.at \
/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