From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org,
 Jonathan Toomim <j@toom.im>
Date: Wed, 28 Oct 2015 07:13:55 +0000
User-Agent: KMail/1.13.7 (Linux/4.1.9-gentoo-r1; KDE/4.14.8; x86_64; ; )
References: <291B85A6-D8D4-443B-B03B-C675CBEEC662@toom.im>
In-Reply-To: <291B85A6-D8D4-443B-B03B-C675CBEEC662@toom.im>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201510280713.56677.luke@dashjr.org>
Subject: Re: [bitcoin-dev] Composite priority: combining fees and
	bitcoin-days into one number
Precedence: list

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