Proposal for changing default configurations

RegisteredFirst TopicFirst Reply10 Posts5 Topics

In v1.1, we’ll be making some changes to default configurations. Here are the proposals: 1. Change `fallbackfee` from 0 to 0.00001, which is 1sat/vB; 2. Change `blockmaxsize` from 300000 to 3985000, which is 3.985MB; `blockmaxweight` from 1200000 to 3985000，which is 3.985MWU; 3. Change `minrelaytxfee` from 0.0001 to 0.00001, which is 0.1sat/vB; 4. Change `blockmintxfee` from 0.0001 to 0.00004, which is 0.4sat/vB; 5. Change `incrementalrelayfee` from 0.0001 to 0.000001, which is 0.01sat/vB; 6. Change `datummdiff` from 65536 to 262144. 7. Change `assumevalid` to `00000000000000000000807f9dc917442a67910426d79ebb2f8aa2149327ce8a`, which is the block hash of height 961631; Welcome to the discussion under this post.

Fri, 09 Oct 2026 02:51:19 UTC · Reply

Edited: Fri, 09 Oct 2026 03:04:29 UTC
Edited: Fri, 09 Oct 2026 05:04:28 UTC

nakamotwoMember

Motivation and reasons: For #1: The default value of `fallbackfee` is currently set to 0. This could lead to a wallet failing to create any transaction if the fee estimator encounters an issue. For #2~5: We believe more transactions per block are preferable. Miners could earn more while users save on costs. For #6: The difficulty of 65536 is too low for mainstream miners today. A 100TH/s miner could easily handle 262144. For #7: This could enhance the performance of IBD. Block #961631 is the latest common ascender of Purity Knots and Core, so it's highly trustworthy.

Fri, 09 Oct 2026 03:09:26 UTC · Reply

potatotomNewbie

i think the blockmintxfee should be <= the minrelaytxfee. It's not clear why we would relay a tx but not mine it. and the blockmaxweight is 3.985MWU, not MB, sorry for nitpicking ;-)

Fri, 09 Oct 2026 04:53:15 UTC · Reply

nakamotwoMember

Yes — 3.985 MWU for blockmaxweight, not MB. Thanks for the correction. I have updated it.

Fri, 09 Oct 2026 05:05:45 UTC · Reply

nakamotwoMember

This default minrelaytxfee is primarily intended for non-mining nodes. A lower value benefits the network. Setting the default blockmintxfee value too low could make it unsuitable for mining nodes. Current mempool data suggests the majority of transaction fee rates exceed 0.1 sat/vB. Transactions with a fee rate above 0.4sat/vB typically fill a block. I would really appreciate it if you could provide recommended values.

Fri, 09 Oct 2026 05:16:49 UTC · Reply

potatotomNewbie

I don't really have any input on recommended values, just, that these, because they are compiled in as defaults, would be sensible ones. What do we want? I think a min relay + min mine fee of 1sat / vbyte makes sense, at least the miners can earn something. but that's just my opinion. And as long as the consensus isn't changed, people can change their defaults anyway. What would interest me much more is much faster block times and probably then reducing max block size, so that it can be used as a peer to peer cash system as Satoshi envisioned. Halving the block time + block size + reward would not increase stress on the nodes significantly. but maybe we can come up with something more clever.

Fri, 09 Oct 2026 06:41:05 UTC · Reply

nakamotwoMember

1sat/vB will stop most transactions. That's unfair to the users and will widen the gap between Purity and legacy chain. Purity is designed for all Bitcoin users. On the other hand, we know node owners rarely change default settings. If some pool earn much more by set to low `blockmintxfee`, that's also unfair to other miners.

Fri, 09 Oct 2026 10:20:57 UTC · Reply

nakamotwoMember

We can discuss those configurations in other posts. It’s interesting although I have different ideas.

Fri, 09 Oct 2026 10:22:29 UTC · Reply

potatotomNewbie

Fri, 09 Oct 2026 06:41:07 UTC · Reply