What are the good arguments for running core instead knots?
Why are people so angry with the knots guys?
Aren't multiple node implementations a good thing?
#asknostr
Login to reply
Replies (17)
I run core AND knots. I don't know why people think they have to choose.
engineering talent behind core is 1000x more than any other team. their reasoning is sound even if unpopular amongst the twitter crowd
Bien, corro amethyst y primal al mismo tiempo 🫡

The arguments don’t seem to be about engineering, they seem to be more about philosophy
It’s really simple, as a man, do you suck cock? If so you need to run Bitcoin Core, if your a woman and suck cock, you definitely need to run Bitcoin Knots
the core people seem split. v.28 vs. v.30
so, there are 3 camps of thought.
Core shit a brick for me after updating so now I’m trying knots.
I’m all for multiple implementations. I would prefer for more to be running btcd or getting a rust implementation ready for prime time. Knots is just a slightly modified lagging version of core.
But the reason I run core over knots is I trust the engineering, code review and release processes that core does.
I also think all this mempool filter changes are us making a mountain out of a molehill.
Core has the track record, the stability, the reliability. And there is no need to run the latest version. For most node runners, an old core node runs fine and you don't need the complexity Knots adds for power users.
Despite having bad mempool weather on occasion, the network still survives.
Still, the controversy around the latest versions of core are sus. I'm unlikely to upgrade past 28 or switch to knots.
For more:
nostr:naddr1qqhyy6t5vdhkjm3dgdhhyefdweej6jmwda68xt2pdck57cn2v43hg6tkv5k5cmm0dvkkkamgx9uk5qgkwaehxw309ash2arg9ehx7um5wgcjucm0d5hsygr76l2u82lsd7suqrm3lpuc2emf734vjg65cy5m8m24vfgxjflzqqpsgqqqw4rscqe4nt
I don’t want btc to become bsv. So knots it is.
“Why are people so angry with the knots guys?”
They have tech-tunnel-vision. Evaluating purely on technical merits is a red herring.
The main driver to Knots (IMO) is not better tech. It is moving away from a perceived corruption of Core devs (right or wrong).
Who gives a fuck about the tech when corporate interference and back room deals are on the table as a possible scenario here?
nostr:nevent1qqs9hvz362xxa9tkfyngm62ew2ghg2g4j90sxyq3svuvtft69gqtslcpndmhxue69uhkummn9ekx7mp0y5erqamnwvaz7tmwdaehgu3wd3skuep0y5erqffjxpshvct5v9ez2v3swaehxw309ahx7um5wgh8w6twv5hj2v3sy5erqctkv96xzu39xgc8wumn8ghj7ur4wfcxcetjv4kxz7fwvdhk6te9xgc8wumn8ghj7un9d3shjtnyv9kh2uewd9hj7ffjxpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9u33j4p5
nostr:nevent1qqs25wxxe3adekvc8x42quv7fr3gpwp7mnu7yg9nuwqmnm88qymtunspp4mhxue69uhkummn9ekx7mqmkv6nv
Knots is is still a fork of Core (merging from upstream), so you get those 1000x IAmVerySmart Dev fixes and additions anyway, plus or minus philosophical differences.
Run your own code
Knots is not "another node implementation", it's just Core with some patches.
Perdona, pero no es una buena comparación.
Amethyst y Primal son dos clientes que implementan protocolo Nostr. Dos implementaciones en código de un mismo protocolo completamente distintas.
Core y Knots comparten 99% del código, ya que Knots se basa en Core y le aplica algunos parches/cambios.
Si crees que los cambios que aplica Knots tienen sentido, corre un nodo Knots. Pero si crees que son cambios inútiles, no hay ninguna razón para correr un nodo Knots si ya tienes un nodo Core, por ejemplo.