There is a meme going around that Luke Dashjr is the only maintainer of Bitcoin Knots. This seems implausible to me with all the attention Knots has gotten lately.

Can anyone point to anyone else who works on it? Or step up and say "Luke is not alone, I work on Knots too"?

Reply to this note

Please Login to reply.

Discussion

Isn't knots based on core? So it's like core does most of the work and then you just need Luke and maybe some others to modify it to be knots.

Yes. There would be no knots without core. Yet the knots followers shit all over core.

It is good to reuse work where possible, but it would be bad imo if only two people were checking to ensure Knots is safe, given the changes made to Core's codebase, and the number of users depending on its reliability. I hope at least 15 people are regularly running tests on Knots, thinking about new tests, checking the quality of the existing tests, and contributing to it on the basis of that research.

I can't claim to know what all the changes entail, but my understanding is that knots primarily changes transaction relaying policies. That logic could be completely jacked and your node would probably still run fine. The tests for that specifically would amount to, "when I hit the node with this set of transactions, are the ones I expect to be filtered out being filtered out?"

I agree that there ought to be more eyes on the diff between core and knots to ensure that nothing beyond non-consensus, non-critical, non-crypto, etc. logic is being changed. The diff between the tests themselves would say a lot.

Bob might Sybil attack Alice

I haven't contributed to Knots as a dev. (I'm barely a dev anyway)

Are you affiliated with knots in any way?

Well... Zero contributors... Push to main... Seems like just him to me.

It looks to me like there are at least two contributors to Knots: Luke and Retroplex. I am hoping to find at least 13 more. nostr:nevent1qqsdx7np8y4hnc5nne9du23v4y25edky4gr6xvznadsq06zyhqd966spr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgszrqlfgavys8g0zf8mmy79dn92ghn723wwawx49py0nqjn7jtmjagrqsqqqqqpghe4vy

When did you look? I looked right before I posted and saw zero contributors. Unless I looked at the wrong repo

Just looking at the app. Maybe desktop is more clear

He is really the only person who's working on Knots. Core does the heavy lifting and he just tweaks it a little.

That's pretty much what Luke is doing. Not knocking the guy but Knots isn't gonna be able to stand on its own if core is gone. Solo maintainer vs multiple people is always a bad sign.

It looks to me like there are at least two contributors to Knots: Luke and Retroplex. I am hoping to find at least 13 more. nostr:nevent1qqsdx7np8y4hnc5nne9du23v4y25edky4gr6xvznadsq06zyhqd966spr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgszrqlfgavys8g0zf8mmy79dn92ghn723wwawx49py0nqjn7jtmjagrqsqqqqqpghe4vy

Two is a good start. If I can get my skill up to par then I'd try to help contribute. I also looked at my wording and it might come off as dismissive of knots. I don't mean it that way. I support Knots and client diversity, just don't want it to be hyped and it being just Luke and the other maintainer and they get overwhelmed by all the things needing to get fixed.

Ironically ataraxia just started working on Knots and he uses a Windows XP avatar

Well I'm glad there's more people on Knots development. I realized my wording isn't the best, I'm not trying to dismiss Knots. But I just don't want it to get over hyped and adding stress to the very few maintainers it has or to possibly have it be another core situation if it gets adopted more. I appreciate you letting us know more info about who's working on Knots. You're the best and I appreciate all the work you do in ocean.

Its not to knock on Luke. There isn't as much activity across Knots development from peeps and no one is really being vocal about it too. Hopefully that changes so there's diversity between clients to help strengthen the network.

It's true, and it's why I don't use knots.

It does not seem to be true. The Knots github lists someone called Retroplex as a contributor other than Luke. It also lists other usernames as code authors, but so far the other ones I've looked at apparently wrote it for Core and then Luke copied their code to Knots too. That's worth something, but in my book it does not count as an intentional Knots contributor unless they looked at Knots while writing it and intended to get it into that codebase.

Retroplex seems to fit that description, which means it is not "just" Luke. I am hoping to find at least 13 additional contributors in the sense which I describe in this post -- that is, people who write code while intentionally thinking about how it would work in Knots and working with Knots to be sure their code will work as intended there.

It's like a modding community instead of game developers

It's not a meme, it's fact, and knots is just bitcoin core with Luke's own selected patches on top.

No, there are other devs working on specifically Knots now.

I found one, a dev with the github username Retroplex contributes to Knots. Can you name any others besides him and Luke?

Retropex is ocean ( nostr:nprofile1qqsz8ffq6k7qcnkvm05826s4x42ejjpvnu6725qn8d6jmwapexzwzkcpzpmhxue69uhkummnw3ezuamfdejszxnhwden5te0wfjkccte9ehhyctwvajhq6tvdshx7angqyxhwumn8ghj7mn0wvhxcmmvv6fwgv)

Others are ataraxia, bigshiny and I see a few more but I haven't checked out what they've had merged.

This ataraxia? https://x.com/009Ataraxi71445

Does he have a github or other link where I cam view his contributions?

Here is his GitHub account:

https://github.com/Ataraxia009

until now all contributions were first sent to core and Luke would merge them to knots. But recent core attitude of rejecting patches that would make forking easier means in future, things may change and devs will be encouraged to directly push patches to knots.

I am personally working on creating a consensus only lib which will be same code base as core but this will allow easier integration of polyglot clients. This way we only "agree" on consensus code and can have our own mempool/wallet etc implementation. people can then choose any non-consensus related implementations and all use the same consensus implementation. I have started looking at the libbitcoinkernel project

This will make maintaining much easier..