Luke has said a lot of things…

Kaspa does.

https://x.com/hashdag/status/2064338133831819591?s=20

https://x.com/hashdag/status/2064338133831819591?s=20

Show me another L1 that does the same? Over emotional much?

All you’ve said is that what if the Devs fork it??? Nobody can disagree! It’s just not true. I’ll say it again. Without a 51% attack, the MuHash written in the header is unchangeable, and the UTXO snapshot matching that MuHash is unforgeable. Does Kaspa have consensus at the moment? Yes. And if your argument is what happens when it doesn’t have consensus? Same as BTC in years past. Don’t run the syncing node if you’re worried about consensus.

Without a 51% attack, the MuHash written in the header is unchangeable, and the UTXO snapshot matching that MuHash is unforgeable. Does Kaspa have consensus at the moment? Yes. And if your argument is what happens when it doesn’t have consensus? Same as BTC in years past. Don’t run the syncing node if you’re worried about consensus.

If you don’t like the syncing node, don’t run it. It’s that simple.

If you don’t agree with a fork, you don’t sync. That’s flatly plain. Idk why that’s contentious.

And sure, if you’re running no downloads on Bitcoin since 2010… give me a break.

You clearly have no idea what you’re talking about.