pull down to refresh

Regarding OP_RETURN drama. What's your move anon?
Update to next version of Core30.8%
Run Knots30.8%
Don't update, stay on Core38.5%
39 votes \ poll ended
150 sats \ 1 reply \ @OT OP 11 May
I think I'll start running Knots. I want to get Datum set up and running. I see it as a higher priority for now.
reply
DATUM is also running with Bitcoin Core, though Bitcoin Knots is recommended: https://github.com/OCEAN-xyz/datum_gateway?tab=readme-ov-file#datum-gateway
Bitcoin Knots in the default configuration requires quite more resources to run.
reply
295 sats \ 1 reply \ @zapsammy 11 May
reply
😆
reply
So far I'm just going to not update. I can afford to wait and see.
reply
This is what I love about Bitcoin. All comers allowed whether you agree or not!
reply
21 sats \ 1 reply \ @Lumor 11 May
Core 0.29 released in mid-April doesn't contain the unmerged pull-request.
reply
Yes.
The change the change looks like it's coming maybe in the next release or one after that.
reply
Stay on core, but maybe update after around months the node with LN on top.
reply
don't update, simple
reply
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
Isn't Knots basically the same as Core with a few extra configurations?
reply
0 sats \ 0 replies \ @anon 9h
TLDR: The volume of the changes in Bitcoin Knots compared to Bitcoin Core makes it practically impossible to audit.

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
0 sats \ 3 replies \ @anon 22h
I do not know. I didn't check. Did you?
reply
0 sats \ 2 replies \ @anon 12h
I mean that I did not check the source code, like to make a diff and evaluate the differences.
reply
0 sats \ 1 reply \ @OT OP 11h
Yeah, I haven't personally. Might be beyond my expertise but I have heard this from multiple sources (devs). I think it's generally understood to be so, it's just that some say that the configurations are "opinionated".
reply
0 sats \ 0 replies \ @anon 9h
I did some comparison of the source code of both and posted in this thread. Note that a single line of buggy code is enough to end up with a remote backdoor, intentional or not.