pull down to refresh

Alternatively:
There have been a total of 42 pull requests opened to Knots. 26 are open and 16 are closed without merge. Not one developer has a merged PR in Knots—not even Luke, who pushes code changes directly to the master branch. You can see this yourself by taking a look at the Knots repo.
#155 – Zero comments, closed by PR author #124 – Declined by maintainer #107 – Retracted by PR author #89 – Review not incorporated, closed by author #86 – Closed without comment #85 – Declined by maintainer #84 – Typo fix picked up in other commit #78 – Merged according to PR author, but via a different commit than the one in the branch #76, #55 – 2× One line to add missing dependency adopted by maintainer #54 – Doc update, unclear whether it was merged #53 – Declined #27 – Closed, issue fixed independently #23 – Declined #13 – PR declined for being obsolete #11 – Declined
100 sats \ 0 replies \ @optimism 3h
You can't really compare a downstream fork (and especially not a rebasing one) to its upstream though, that's not apples to apples, because the fork can (and often does, also outside of this particular instance) include all or much of the upstream work too. Besides, Core is still the reference client, so you can't really compare any other Bitcoin client to that.
What you can do is compare btcd to libbitcoin, or compare knots to Peter's libre-relay if you want apples-to-apples.
reply
0 sats \ 0 replies \ @BITC0IN 2h
Congrats
reply