Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed;
	boundary="Apple-Mail=_CFEF61F8-F305-4AE2-949C-CB82C81BF0D6";
	protocol="application/pgp-signature"; micalg=pgp-sha512
From: Jonathan Toomim <j@toom.im>
In-Reply-To: <201510280713.56677.luke@dashjr.org>
Date: Wed, 28 Oct 2015 15:41:39 -0700
Message-Id: <554CB626-4CCC-4607-9A1F-E583A52989A6@toom.im>
References: <291B85A6-D8D4-443B-B03B-C675CBEEC662@toom.im>
	<201510280713.56677.luke@dashjr.org>
To: Luke Dashjr <luke@dashjr.org>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Composite priority: combining fees and
	bitcoin-days into one number
Precedence: list


--Apple-Mail=_CFEF61F8-F305-4AE2-949C-CB82C81BF0D6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Oct 28, 2015, at 12:13 AM, Luke Dashjr <luke@dashjr.org> wrote:

> On Wednesday, October 28, 2015 4:26:52 AM Jonathan Toomim via =
bitcoin-dev
> wrote:
>=20
> 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.
>=20
> 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.

I think the only custom policy that this change would make harder to =
implement is the current default policy of 5% reserved space. Right now, =
in e.g. CreateNewBlock, you have two loops, each of which follows a =
completely different policy, plus additional code for corner cases like =
ensuring that a tx isn't added twice. If I were a miner and a mediocre =
programmer (which I actually am, on both accounts), and I wanted to =
change the mining policy, I would probably take a look at that code, =
groan, give up, and go sharpen my pickaxe instead.

This change could be written in an abstract way. We could define an API =
that is calibrated on the whole mempool, then has a method that takes =
transactions and returns priority scores.

If someone wanted to write a reserved-space algorithm in this priority =
API scheme, then they could just set it up so that most transactions =
would get a priority score between e.g. zero and 8999, and any =
transactions that were supposed to be prioritized would get a priority =
level over 9000. Easy enough?


--Apple-Mail=_CFEF61F8-F305-4AE2-949C-CB82C81BF0D6
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJWMU8jAAoJEIEuMk4MG0P1zHUIAIV/s2lNMDNf470evjWPFXMK
Md0xyY4yXk0goPIaME1WjVyqCrFlRqCbn6oRxQGFV3XiOP3gITC4rJO9cY4Mcr0y
pCA5BAROUI/uXBo4eOFIDlJZ98N8D3luZ2P5pX/KdGaK49unFuKrqB7wbZTHjA1t
bBwyb9vwRvAHgEoFvKAga/aRx1hjQ/VCJyIRvh70TJzcMAIccyIPTYUEHQY8sakD
J+lo1Y9nCZOu4f6bY/S0JiYBU25ot5OI3mvLBbBBPiU3pnhjGDppCyJTRk66RNY8
xxLlCSJVGDa/6ScCtjAILck+a75Y3uIxZXbzwhpQXpUCdpYIFqfGQH9Sa4oPgoI=
=8alk
-----END PGP SIGNATURE-----

--Apple-Mail=_CFEF61F8-F305-4AE2-949C-CB82C81BF0D6--