#Bitcoin Knots is a single developer ripping commits to master without any review process.
The repo is 2500+ commits behind Core. Just Luke shooting from the hip; anything he wants goes.
I'm no fan of Core's latest shitshow with OP_RETURN, but Knots is a project so centralized that Luke, who couldn't even custody his corn properly, is the alpha and omega of every decision and change made to the code.
Yeah... I'm gonna pass on that.
Helpful reality check, thanks 👍
You’re saying keeping your bitcoin secure is more important than making a point on the current drama? So selfish😂
💯
Im just hunkered down in 26.0 until this is all sorted.
Team do nothing FTW.
V. 26 still have the datacarriersize bug
Say more for those of us who are regarded.
It’s actually pretty simple. Back in 2023, spammers figured out how to bypass the datacarriersize filter in Core. That loophole made it easier to deploy ordinals and inscriptions by injecting arbitrary data into what appeared to be legitimate monetary transactions.
Some users raised the issue and submitted a PR to Core to patch the bug and stop the abuse of nodes. Core shut it down, calling it “controversial.” Later, someone discovered that Core had already realized datacarriersize wasn’t functioning properly and quietly edited the filter’s description to retroactively justify not fixing it.
When they got called out on it, one of the maintainers even claimed that changing the description counts as a valid way to fix a bug. That vulnerability is still present in earlier versions of Core and you can’t simply make it work.
Reasonable
Good point. In fact, seems the safest thing to do is not doing anything. No need for updating your node for the moment.
Bad take. Knots is a fork of core, meaning its codebase is the result of every core dev code commit + nostr:nprofile1qqs0m40g76hqmwqhhc9hrk3qfxxpsp5k3k9xgk24nsjf7v305u6xffcppemhxue69uhkummn9ekx7mp0qyxhwumn8ghj7cnjvghxjme06q3qnf's on top of it. Not to mention Luke has made dozen of bug fixes in Knots compared to Core. If you are not happy with him having the final say, that’s ok and I think other implementation besides Core and Knots are a good idea, but when you weigh in the tradeoffs Knots is the lesser evil at this very moment.
nostr:nprofile1qyvhwumn8ghj7ctyw4k8gt338pcxcatn9eek7cmfv9kqz9nhwden5te0v96xcctn9ehx7um5wghxcctwvsqzpmc4r3arsr6q5awh69yn4s68kemh48vmt7s250xak3lu0ratdx5tz27l4q nostr:nprofile1qythwumn8ghj7cnfw33k76twv4ezuum0vd5kzmp0qy88wumn8ghj7mn0wvhxcmmv9uqzq7el0qph2p6x7325zw3zr7qfvhhvk600xz8jatga4zwv9jy396tgl0dzev nostr:nprofile1qythwumn8ghj7ct5d3shxtnwdaehgu3wd3skuep0qyt8wumn8ghj7ct4w35zumn0wd68yvfwvdhk6tcqyp60l3gucvq4pnmekm9nzmf6zh8nx24jngu0aj0tfp9tz4gad5v9v94ulq2 nostr:nprofile1qyv8wumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wsq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgqgzx3h . . . any response?
Is their Github just a mirror? All I see is Luke cowboy committing directly to the master branch.
True! 🤷♂️ Too centralized since there is a person in charge behind that project
