Different implementations are non-partisan and perfectly fine as long as consensus rules match. Like you said, Knots is basically Core with extra relay options, and for Core/Knots team to deviate into hard-fork territory would be an insane move, and bad for Lightning.
The good thing about Bitcoin is we don’t have to speculate on compromised teams or people; the code speaks for itself, and everyone is free to choose which open-source software to run.
Knots is already bad for lightning, not when it hard forks. Same for older versions of Core
I think it matters more than you’re stating. I’m not going to pretend I understand the ins and outs
I also don’t think it’s a pressing existential issue now but it could become one in the future
Yeah, that’s true with the relay policy mismatches.
You’re right, Core 30 will roll out no matter what with its own policies too, and hopefully it doesn’t escalate further
