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 23h
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 17h
Core 0.29 released in mid-April doesn't contain the unmerged pull-request.
reply
0 sats \ 0 replies \ @OT OP 15h
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
0 sats \ 1 reply \ @anon 1h
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
0 sats \ 0 replies \ @OT OP 1h
Isn't Knots basically the same as Core with a few extra configurations?
reply