From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org, Jonathan Toomim <j@toom•im>
Subject: Re: [bitcoin-dev] Composite priority: combining fees and bitcoin-days into one number
Date: Wed, 28 Oct 2015 07:13:55 +0000 [thread overview]
Message-ID: <201510280713.56677.luke@dashjr.org> (raw)
In-Reply-To: <291B85A6-D8D4-443B-B03B-C675CBEEC662@toom.im>
On Wednesday, October 28, 2015 4:26:52 AM Jonathan Toomim via bitcoin-dev
wrote:
> Assigning 5% of block space based on bitcoin-days destroyed (BDD) and the
> other 95% based on fees seems like a rather awkward approach to me. For
> one thing, it means two code paths in pretty much every procedure dealing
> with a constrained resource (e.g. mempool, CNB). This makes code harder
> two write, harder to maintain, and slower to execute.
This is all in the realm of node policy, which must be easy to
modify/customise in a flexible manner. So simplifying other code in a way that
makes the policy harder to configure is not a welcome change.
That is, by making the code simpler, if you make custom policies (such as the
current default) harder, it is better to leave the main code less simple.
Luke
next prev parent reply other threads:[~2015-10-28 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 4:26 Jonathan Toomim
2015-10-28 7:13 ` Luke Dashjr [this message]
2015-10-28 22:41 ` Jonathan Toomim
2015-10-29 0:55 ` Luke Dashjr
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=201510280713.56677.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=j@toom$(echo .)im \
/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