So in your view we should not anticipate, and only act when itās already too late.
Ok yeah disagree.
But the good news is you donāt have to upgrade if you donāt want to! :)
Discussion
So thereās no middle ground for you?
Youāre saying we must act on potential problems nowābefore they existābecause once we see them, itāll be too late?
No.
You anticipate problems, draft possible solutions, and keep them ready. If an issue actually emerges, the community reaches consensus and implements the best fix.
What youāre proposing is gaslightingāa trojan horse for more āfixesā to problems that donāt exist.
The good news? Iām running Knotsāa real solution to a real problem: a rogue core team trying to strong-arm and gaslight the network into compliance.
Youāre solving nothing. Thereās no problem to fix. Either focus on real issues or find hypothetical ones that actually matter.
> core team trying to strong-arm
How? :)
By trying to force changes to the software that a massive portion of the community vehemently disagrees with. They have not proven these changes will help, and they have not addressed the potential problems the changes may cause.
What they propose involves philosophical changes to fix potential problems that do not exist at this time.
We don't need that on layer one. We need to leave layer one alone until actual problems begin to surface.
What's your take on the ~1500 unreviewed commits that Luke forces on Knots users? And how do you even know what's in these committs?
"Iām running Knotsāa real solution to a real problem" ššš
What's the problem?
These are not potential problems. We already saw this play out during a spam hype in 2015. Spammers moved to fake key outputs, which lead to unnecessary permanent bloat utxo set bloat. It is likely that such a cycle will occur again that it happened three times already now.