pull down to refresh
0 sats \ 6 replies \ @anon 12 May \ on: On Nodes - Your Next Move AskSN
I am not sure people realize how centralized is the development of Knots. There is very little if any code review and a single person with write privileges to the repository.
I guess he can sneak a malicious code any moment without people noticing. He or somebody else if his account gets compromised. And his accounts were compromised in the past, when his Bitcoins were stolen.
I hope the above poll is not representative and 30% of the network will not run Knots just for this reason alone. Nothing against Luke and I am no taking sides in the OP_RETURN debate.
reply
TLDR: The volume of the changes in Bitcoin Knots compared to Bitcoin Core makes it practically impossible to audit.
This is a comparison from Knots' web site: https://bitcoinknots.org/files/28.x/28.1.knots20250305/bitcoin-28.1.knots20250305.desc.html
Then some stats locally:
# add the remotes
$ git remote add bitcoin https://github.com/bitcoin/bitcoin
$ git remote add knots https://github.com/bitcoinknots/bitcoin
$ git log --format=oneline v28.1..v28.1.knots20250305 |wc -l
1370
$ git log --format=oneline v28.1.knots20250305..v28.1 |wc -l
0
So, for v28.1, Bitcoin Knots is Bitcoin Core + 1370 more commits. What are those 1370 commits?
$ git diff --shortstat v28.1..v28.1.knots20250305
550 files changed, 25871 insertions(+), 2640 deletions(-)
So, 550 files have been changed, with about 25k lines of code being added.
reply
reply
reply