"UTXO-based model is the right model" - programmable tickets validated and ordered on-DAG, at scale.

a few unrelated observations/notes 1. @manyfest_ recently made me realize that beyond the obvious point that covenants on Kaspa can serve as first class state machines, they also have 2 significant properties: • they are lightweight: on chain we store commitments to

@ibuypow 100%. realtime is speed, and 'realtime decentralization' achieves it in a decentralized manner. but that's just the easiest application to convey. a broader implication is the scope of actionability that you can delegate to the realtime engine. for instance, assume we want to

Dagknight technical progress As would be mentioned in a still unshared post by @michaelsuttonil, the dagknight effort is split into v0 devnet, v1 testnet and v2 mainnet candidate. I’ve been testing the current v0-based implementation in a small devnet with the help of some

Kaspa is real-time bitcoin, solving scalability is great but not the core value prop. Real-time bitcoin means achieving in a few seconds the same security guarantees that nakamoto consensus / bitcoin achieves after an hour; decentralizing each consensus round rather than chain

In 10 years, Kaspa will be quantum-resistant and run the largest consensus network. Bitcoin? It’ll struggle to keep up. Some will cling to pride over progress, refusing hard forks… while Kaspa moves forward.

https://t.co/f06KAcpUGV

Releasing the judges panel - 7 legends actively are reviewing all of the amazing Kaspathon submissions. @JC_G33K @eliottmea @MerlinNobody @emdin @KaspaQueeen @asaefstroem @kaspador_ ps: list order has been randomized, order doesn't matter, dedication does and they all are.

So here's another—rather technical—component of the L1<>L2 design puzzle: The canonical bridge (entry/exit mechanism); see link down the thread. Context We are designing the bridge to support based zk rollup systems over Kaspa. We focus on the “based” setup as a first-class

DONE. Just completed an initial working implementation of a based zk covenant/rollup with KAS canonical bridging (over TN12 capabilities). This work is part of the covenants++ hardfork milestone roadmap( https://t.co/uMtcOLvgMo) The work is scoped as PoC however all significant

I've used $KAS more in the last week than most Bitcoiners have used Bitcoin since 2009. Every message sent through @KaChat_ rewards the miners. More apps are being built on #Kaspa Yeah, $KAS works and it's here to stay.

A handful of Bitcoin Maxis have been messaging me recently asking about $KAS... They are starting to see the cracks in Bitcoin. But they're too afraid to talk about #Kaspa publicly. He plans to allocate 6-figures to $KAS as a hedge against Bitcoin failing. This person has a

Kaspa dev Michael Sutton broke down the smart contracts roadmap in a thread. Kaspa right now is basically cash. You send it, someone receives it, done. No logic sticks around after a transaction. Covenants change that. New opcodes let coins carry rules forward. "You can spend

not sure if it was clear, but all of this is already implemented and running on Kaspa’s testnet 12 (TN12), for the record <3

@moshikrl @kaspaunchained @michaelsuttonil aiming for two HFs in 2026, cov++ beginning of May, DK+increased BPS end of Q3 god willing. both are aggressive timelines, but realistic with the newly expanded devforce

This is a serious engineering achievement. Mastery of Kaspa script engine intrinsics + zk guest-program complexity, shipped end-to-end in ~6 weeks. Hats off @Max143672

“We won’t attract capital by vibecoding 2020 products with a “decentralized” deck. We need products that make unique sense on $kas.” I’m ruined, my 200$ spent on claude … On a more serious note, can someone just reach out to wikipedia and to Oxford English Dictionary and

Kaspa Core and community members are actively discussing future fee market sustainability. Here are some places to tune into the conversation. Fee Mechanism Discussion - https://t.co/p7kaHRdNoA Round Based Monopolistic Price in Kaspa - https://t.co/yc5qXoI0TL Noise-Tolerant

Kaspa’s evolution: from local scripts to stateful systems, without losing locality I want to try to explain, in simple words, the vision and the gradual implementation path for smart contracts and complex financial systems on Kaspa. Instead of trying to cover everything, I am

🚀 Stablecoins Coming this month on #Kaspa! @kasplex testing #USDT & #USDC on mainnet. Trade. Build. LP. Fastest PoW network. 💥