Decentralisation in Bitcoin's codebase comes from the ability of anyone to release their own reference client, that enforces the consensus rules, as they see fit.
Users are divided, at this time, over the legitimacy of 'inscription' transactions.
All Bitcoin Knots is doing, is giving users a simple way to vote with their feet.
This is the free market, in action.
If you do not agree with the consensus implementation, don't run the code.
This applies equally to all Bitcoin reference clients. Be it Core, Knots, or otherwise...
It's worth noting you still can configure the limit however you want in Knots. This fix just means it will actually honour your choice.
I would like those two limits to be separate.
Based on discussion about it and not actually having looked at the code yet, it gives more control to the individual, something you should be for given your values.
If the premise is true, that an individual nodes carry limit can be ignored, this is forced association.
The size can also be adjusted back to the larger, inscription accepting size.
Basing my conclusion on this:
nostr:nevent1qqs2fpcdf0f73vypysyeywhrpdnek0sqxstprhvcvl0dtpwmf84xxvspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg8a6h50dtsdhqtmuzm3mgsynrqcq6tgmznyt92ecfylxgh6wdry5upsgqqqqqqstupe6q
Oddbean new post about login | logout