In a few years, when everyone is sick of their antics and drama, all the Knots users will have abandoned ship and gone back to Bitcoin Core.
Login to reply
Replies (20)
*crickets chirping*
Face it, you’re the new bcashers. And Mechanic is the new Roger Ver.
[pause] *crickets chirping*
If only you guys had the balls to actually block JPEGs and fork the blockchain, instead of just hiding behind your weak “filter the mempool” b.s.
Aka accomplishing nothing but virtue signaling.
Scared of a project that copies practically all its code from them? 🤣🤣
You really are the new bcashers.
That’s the beauty of it. He accepts all contributors work and then strips out the chicanery and politics. And there’s nothing you can do about it.
Luke? He literally couldn’t even keep his own bitcoin safe from hackers! 🤣🤣🤣
Well… the only people with the motivation, insight, and access to pull off such a theft…
Gimme a fuckin’ break. Luke is a moron that should’ve known not to keep the entirety of his wealth sitting in a hot wallet on his home server.
The fact that you are trusting bitcoin protocol development to someone with that little common sense is incredibly moronic.
I’m not at liberty to discuss an ongoing investigation but you seem to know a lot about it.
Why don’t you start front the beginning and tell me the whole story.
Luke got hacked cause he’s a dumbass who kept his private keys to an enormous stash sitting on a home server.
He has a long history of terrible judgement. Remember when he wanted to change Bitcoin’s POW algorithm from SHA-256?
What was his rationale for that?
He’s an idiot, who cares?
And now you’re running a bitcoin node that he is the sole maintainer of.
Explain it to me, or you could just say that you dont know.
Nobody knows who hacked him. Any sophisticated hacker could’ve potentially pulled it off. Regardless, his security practices was poor.
No, I mean changing the pow algo from sha-256
It’s a lunatic idea, who cares?
Can you explain this? Doesn’t seem add up.
Explain what?