kiwi's avatar
kiwi 2 months ago
“Every single node operator should run Knots to signal” No. The default is to not update. Every [existing] node runner (prior to v30) should take this stance until being convinced of upgrading (whether to v30 or knots). Most node runners are technically incompetent. Knots is not a single line of code changes, but thousands of lines of code changed. Node runners who are unable to quantify the merit of these differences should not change to [virtue] “signal”, especially without being able to quantify said changes. Furthermore, it is seeming that you can merely change the data carrier size in v30 still, therefore, wouldn’t the better option be to still run v30 if you see the need to update and merely change that single configuration? The amount of people virtue signaling and cancelling others, over mere policy (not consensus) changes, when we (most of “us”?) want multiple and different clients anyway is absurd.

Replies (1)

Default avatar
uhrrf 2 months ago
Data carrier size in v30 doesn't mean the same thing as it did in v29. Core changed it such that restoring the parameter to 83 in the v30 config does not restore to the v29 (default) behavior. There's info about this on nostr and of course the core github.