Luke Dashjr [ARCHIVE] on Nostr: ๐
Original date posted:2015-10-28 ๐ Original message:On Wednesday, October 28, ...
๐
Original date posted:2015-10-28
๐ Original message: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
Published at
2023-06-07 17:43:57Event JSON
{
"id": "c8ab0c82754988106cefe7941fb467996e601c3b2f207219e0bc7ccea515c2a0",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686159837,
"kind": 1,
"tags": [
[
"e",
"93557ab0aef94db809afdc494022874351bbc3b58a89c29ef9856e022ac0eb23",
"",
"root"
],
[
"e",
"3799a7bfd50401bba31a0b17386586d24d528b90ea097da75a738c93b92a7ca8",
"",
"reply"
],
[
"p",
"0ff56c09ef879c89ea04bfa2d5f5e0d96000ed6eaf5ac38e7b538a9d92767569"
]
],
"content": "๐
Original date posted:2015-10-28\n๐ Original message:On Wednesday, October 28, 2015 4:26:52 AM Jonathan Toomim via bitcoin-dev \nwrote:\n\u003e Assigning 5% of block space based on bitcoin-days destroyed (BDD) and the\n\u003e other 95% based on fees seems like a rather awkward approach to me. For\n\u003e one thing, it means two code paths in pretty much every procedure dealing\n\u003e with a constrained resource (e.g. mempool, CNB). This makes code harder\n\u003e two write, harder to maintain, and slower to execute.\n\nThis is all in the realm of node policy, which must be easy to \nmodify/customise in a flexible manner. So simplifying other code in a way that \nmakes the policy harder to configure is not a welcome change.\n\nThat is, by making the code simpler, if you make custom policies (such as the \ncurrent default) harder, it is better to leave the main code less simple.\n\nLuke",
"sig": "0a6f9ae9297bbd5ab09bb35d6b252126706306cafb1547e56d5eabc7e45283dbce8c6a5e4e082f064a75cd094c5bb236f697da6c4ab8a39c6d2606fd120a5274"
}