Big congrats to the $QUBIC team for resolving this issue so quickly! You guys did an amazing job! I was honestly losing faith, but well done! Especially to the core dev, Joetom. Everyone is going to get their funds back, and for those questioning decentralization, this was a decision made by a group of computers that don’t know each other. Centralization is when one person or entity controls a network. This is not what happened here. And do not confuse decentralization with chaos.

The funds are contained Computors coordinated a protective halt of the network at tick 85,371,949. No transactions are processing, so the drained funds cannot be moved or sold while this is resolved.

kaspa is an open network for money and apps, secured by proof of work. you can transact without needing anyone’s approval. devs can build assets and contracts with rules the network itself enforces. miners compete to produce blocks through computing power and electricity, not the size of their KAS wallet. an attacker trying to undo a confirmed transaction has to compete against the combined mining power of the entire honest network while it keeps mining. even then, they can’t make nodes accept transactions that break the rules. kaspa includes and orders blocks mined in parallel, so miners blocks aren’t discarded simply for losing a race. those frequent blocks let the network reach agreement in seconds while keeping bitcoin’s proof-of-work security principles. kaspa calls this real-time decentralization.

To be frank, joining this forum comes with some discomfort for me. I’m used to taking ownership of core tech that might otherwise remain unbuilt (compilers included). Taking part in ecosystem-wide coordination is a different kind of ownership, and not one I seek for its own sake. But as Kaspa’s native application layer grows, shared conventions are becoming too important for us to simply assume they will emerge on their own. When gaps persist, those with the relevant knowledge should take responsibility rather than wait. My ideal outcome is for serious contributors from across the ecosystem to join, take real ownership of the work, and eventually make my role here unnecessary. That would be a sign of success to me.

When made a decision to be merged mined with kaspa:native from block 1, our own miners were unhappy - they would receive more $ZKAS if we stayed on own algo or on KheavyHash without merged mining. We chose this way to reward #Kaspa miners to partially solve its network security problem - help where we were able to. Every hate message we get is a message to any developers who are building for/with Kaspa. Highly appreciate those who see positivity in ZKas or just watch it neutrally. We will keep building ZKas - fastest privacy L1.

$KAS What’s your take on Bitcoin BIP-110?Feels like it could have serious implications either way. A chain split around late Aug / early Sept isn’t impossible. Curious how this plays out...🤔