i do not think “the majority of core devs are compromised”
i do not think its possible to stop inscriptions even though i wish they were not possible
i do not think it is safe to have the majority of the network run software that is maintained by a single individual
i do think node operators should have more choice and the best path forward is fostering well reviewed alternatives to core
Login to reply
Replies (4)
Bitcoin Knots is not maintained by a single individual.
At least 10 devs deliberately contribute to Knots:
1 x.com/LukeDashjr, https://github.com/luke-jr
2 x.com/leo_haf, https://github.com/retropex
3 x.com/bigshiny90, https://github.com/bigshiny90
4 x.com/009Ataraxi71445, https://github.com/ataraxia009
5 https://github.com/pithosian
6 x.com/cguida6, https://github.com/chrisguida
7 x.com/1440000bytes, https://github.com/1440000bytes
8 x.com/dr0ther, https://github.com/dr0ther
9 x.com/Kurtis_NZ, https://github.com/KurtisStirling
10 https://github.com/kwsantiago
Any others?
View quoted note →
What evidence do we actually have that Core has multiple devs? I mean, it could be like the mining situation - many names, sharing one template. The devs are many names, but one groupthink? Or worse, how do we know its actually them pushing the code? Anyway. Personalities don't matter. There needs to open competition between different implementations competing for maket share of the userbase. 21% of the network migrated to knots within one (?) release cycle - despite the dev concentration risk. That tells you a lot. The plebs have signalled: competition has begun massively. Bullish af. I'd love to see eg 5 implementations with at least 10% share each. Each side is going to have to up their game to grow market share now. Complacency is gone.
Yeah I was glad to see this. Kudos to those contributors!
Yes, new standalone node implementations. But Knots > Core, very clearly for now