Kaspa News - Kaspa articles and recent Kaspa updates

Ori Newman

@OriNewman

Seven months since the first commit, and after an extensive review and standardization process (thanks to @manyfest_,@iziodev,@michaelsuttonil and @asaefstroem), I'm publishing a release candidate for Silverscript v1. The last merged PR was written by @michaelsuttonil and numbered #235, which is a nice reminder to the fact that Silverscript started as my (someone235) project and is now becoming a project involving the entire Kaspa community. You can find a link to the release candidate in the reply, and I'd love to hear the community's feedback. If we don't receive any substantial feedback, we'll release Silverscript v1 for mainnet use one week from now.

Knitser

@0xKnitser

Everyone is debating how KRC-20 tokens should migrate to covenant native KCC-20. We stopped debating and ran one on Kaspa testnet-10. One snapshot, sealed into the token's identity at birth. Every balance claimable exactly once. Zero admin keys after the handoff. Not a bridge, no operator, no committee. Kaspa consensus enforces every claim itself. Five real transactions, all public: token genesis, controller genesis, reserve handoff, a Merkle claim, and the claimant spending what they claimed. See it live and click every receipt yourself: Honest print: the run used one synthetic holder, KCC-20 is still a draft standard, and this is testnet. The mechanism is proven. The rest is verification work, and it is listed on the page. kaspa:native #Kaspa #KRC20 #BlockDAG #KCC20

Kaspa

@KASPAglobal

The blue set is how the network agrees on "the real history" without a leader Every block in the DAG gets sorted into either the blue set, the chain of blocks the ordering rule treats as honest and canonical, or excluded from it. No single node or miner decides that split. It falls out of applying the same ordering rule to the same DAG, which is why two honest nodes reach the same answer without talking to each other first. $KAS

ꓘasparium

@Kaspacryptoking

bitcoin:native solved digital scarcity by making you wait. One block every ~10 minutes. Every competing block that shows up at the same time gets discarded "orphaned" because the chain can only have one winner per slot. That's the tradeoff that's kept Bitcoin secure for 15+ years, and also the reason it can't move fast. kaspa:native asks a different question: what if you didn't have to throw those blocks away? Its GHOSTDAG protocol (Greedy Heaviest-Observed Sub-Tree DAG) lets multiple blocks exist in parallel and still be ordered into a single, agreed-upon sequence. Instead of a chain, you get a BlockDAG — a directed graph where near-simultaneous blocks are all kept, all counted, all secured by the same proof-of-work miners have trusted since 2009. The result: ~10 blocks per second, confirmations in seconds instead of up to an hour, and no wasted mining work — all without abandoning PoW for something unproven. Study Kaspa 💚

ItsFrank

@FrankLambeek

Hey everyone, kaspa:native still stands out in this market. Kaspa is not trying to replace Bitcoin. It is asking a harder question: can proof-of-work stay the core and still settle like the internet? 🟢 Pros • BlockDAG + GHOSTDAG → 10 blocks/sec, near-instant first confirmations • Pure PoW, fair launch, no premine, no VC allocation • ~96% of supply already mined • Toccata live: covenants, ZK verification, programmable UTXOs • Early Igra L2 flow and KaChat starting to create real use 🔴 Cons • Native smart-contract depth is still thin • Developer and DeFi gravity lag the architecture • TVL and liquidity do not yet match the tech • Usage is still more thesis than habit • Security budget tightens as emissions keep falling My take: Bitcoin proved PoW can be money. Kaspa is testing whether PoW can also be infrastructure. That is the $KAS experiment worth watching. What are your thoughts on $KAS?