I’m not ok with a “bitcoin committee”
nostr:note1k3ew2rvtvceesm02ace3wn7sa7p9d0qp4m46jz78gtc8nwphyrdqs8ank6
I’m not ok with a “bitcoin committee”
nostr:note1k3ew2rvtvceesm02ace3wn7sa7p9d0qp4m46jz78gtc8nwphyrdqs8ank6
No rulers
This is horrible fucking idea
It’s a psyop
Is it? Like Im asking seriously. I dont pay much attention to this shit.
Yes it is.
Both knots and core remain compatible with Bitcoin.
There are now multiple client implementations- due to the proposed changes to mempool policy by b-core.
*note:
This mempool change does NOT make the node incompatible with Bitcoin.
Nevertheless, there has been an extreme rejection of this mempool change by users who “run knots”
No one is arguing for a hard fork, the fear mongering suggesting that knots “will” argue for a hard fork in the future is ridiculous and does not represent the intentions of users running knots software today.
Cool. I dont who this person is but it wouldnt surprise me if someone did try to pull something like this at some point, but you know more than on this so I'll take your word for it 🫡
Glad I can help but don’t take my word for it, run your own node and always ensure it remains compatible with the original satoshi software version.
Never update your node software without reviewing it first.
Use ai and crowd source for help reading code. 🫡
This is a weak and pathetic psyop attack from the b-core supporters.
“Running Knots” means a client flag name change- its intent is to show disapproval of b-core like what happened with the UASF.
(CURRENT B-CORE DEVS ARE THE TRUE BITCOIN COMMITTEE BTW)
It’s childish to suggest that now, people who flag knots are somehow also in support of a new altcoin.
Luke’s character or past actions has actually zero relevance to the current flagging protest.
No way
Pretty easy to avoid. Don’t use an bitcoin implementation controlled by one quirky person with no formal review process. 🚁🤷♂️