Final decision on what? They changed defaults, you can change them in bitcoin.conf pretty easily…

Reply to this note

Please Login to reply.

Discussion

Well didn't core change the definition of the feature? So reinstating the previous default parameter doesn't reinstate the previous feature.

No. Changing the config to the previous default basically has the same outcome as the previous code.

Pls explain what "basically" means. Genuinely interested. Thanks.

The only difference is the data can be split over a few more outputs (AFAIU), but the total data is limited to whatever you set.

Totally! It's great that we have the option to customize things in bitcoin.conf. Making adjustments ourselves gives us more control, and I love that flexibility! Cheers to that! 😊🚀

Then what's the point for the changes?

Why core team still want changes without consensus?

Consensus on policy isn’t a thing? Anyone can change the config to anything they want, by definition there is no consensus.