📢 #Dagknight Dev Update
@michaelsuttonil has shared a brief update on DAGKnight development:
“heavy wip. 6 milestones defined.
first 2 are:
incremental algos (pseudo code and analysis showing incrementality also under worst-case scenarios)
testnet (unlike devnets, this means no security relaxation)
both are progressing very well”
So six milestones have now been defined. We know the first two.
1. Incremental algorithms
Kaspa’s DAG is constantly growing as new blocks arrive. DAGKnight needs to process that new information continuously and efficiently.
This milestone focuses on the algorithms, pseudocode and analysis required to show that DAGKnight can operate incrementally, including under worst-case scenarios.
Simply put: DAGKnight needs to keep up with a live, continuously changing DAG.
The reference to “worst-case scenarios” seems to indicate that the analysis extends beyond normal network operation into more difficult conditions.
⛏️For Miners, 🧑💻Makers and 🤖Machines, this is foundational engineering work. DAGKnight needs an implementation that can continuously process an evolving DAG while maintaining the properties established by the protocol.
Specific performance characteristics will become clearer as more of the work is published.
2. DAGKnight Testnet
The second milestone takes DAGKnight into a distributed testing environment.
Michael adds an important detail:
“unlike devnets, this means no security relaxation”
Devnets provide developers with a flexible environment for building and experimentation. A DAGKnight testnet would operate without relaxing the security requirements DAGKnight is designed around.
Simply put: run DAGKnight across a real distributed network while keeping its intended security assumptions intact.
For Makers, this provides an environment for implementation, experimentation and testing.
For Miners and Machines, it provides an opportunity to observe DAGKnight operating across a distributed network under realistic security constraints.
For 🏪Merchants and 🏢Movers, the longer-term relevance comes from DAGKnight’s core objective: confirmation confidence that adapts to observed network conditions. The practical implications for applications and confirmation policies will become clearer through implementation and testing.
🧍♂️🧍♀️For everyday Kaspa users, nothing changes yet. These are development milestones. They show DAGKnight progressing from consensus research toward working network software.
Milestone 1: Make DAGKnight work incrementally as the DAG grows, including under worst-case conditions.
Milestone 2: Put DAGKnight on a testnet without relaxing its intended security requirements.
So,2 of 6milestones defined, with both reportedly progressing very well.
Kaspa devs: help us unpack this further. What exactly falls under “worst-case” incrementality? What will distinguish the DAGKnight testnet technically? What will developers be able to test, measure or build once these milestones are reached?
And we’d love any insight into what might be behind milestones 3 through 6.
$KCOM Is Launching on Kaspa L1
KaspaCom’s ecosystem utility token will launch natively as a KCC20.
The first major ecosystem utility token on Kaspa L1.
Kaspa is our home. $KCOM is coming home. ⚡️
A massive THANK YOU to Shai Deshe Wyborski for everything he has contributed to #Kaspa. 💚𐤊
From deep technical research and GHOSTDAG, to development, education, countless explanations and years spent helping people understand what makes Kaspa special — Shai’s fingerprints are permanently part of this project’s history.
Regardless of where the journey takes everyone next, contributions like these deserve to be recognized and remembered.
Thank you, Shai. For the research. For the knowledge. For Kaspa.
$KAS 💚
Do you see this? The @KaChat_ app just managed to quickly onboard a new Kaspian. ChangeNow swap got him his first bit of Kaspa. The swap feature has a toggle to auto add to your portfolio for tracking.
kaspa:native has been missing a juicy app that does it all doesn't require any questions asked. I intend to keep building!
Enough explaining about Kaspa lets get people experiencing it!
KaspaCom: One home for everything Kaspa. ⚡️
DeFi. Memes. NFTs. Wallet. Tools. Education. Utility.
Building more ways to bring users, builders, and activity to Kaspa.
All products. All Kaspa. One home: https://t.co/Zfz1FtftZO
🚨 $KAS IT'S HAPPENING
This is from Gemini itself. You know who quote retweets posts from Gemini?
The Winklevoss twins.
Awareness of Kaspa is an understatement. The twins call the shots. Keep an eye out.
Kaspa launched without a premine, presale, or insider allocation.
Since genesis, KAS has entered circulation through open PoW mining. That makes mining part of Kaspa’s issuance model—not just another way to acquire the coin.
Explore KAS mining: https://t.co/YEA9p8jfUE
#KuCoin #KuMining
Out of the top 100 coins, only 6 are real crypto (fair launch + PoW + no corporation):
bitcoin:native, litecoin:native, $DOGE, monero:native, bitcoin-cash:native — all launched before 2018.
Kaspa is the ONLY modern entry. 10 blocks/sec on L1. ~6,000x faster than Bitcoin.
Position accumulates.
Framework holds.
kaspa:native
What is Kaspa Silverscript?
@kaspaunchained recently announced that the Silverscript v1 release candidate is live ahead of the mainnet launch.
But what is it?
Simply put, Silverscript is Kaspa's first high-level smart contract language and compiler;
With Silverscript, developers can write clear covenant contracts that compile straight to native Kaspa Script, without a virtual machine, a second execution context, or global account state.
- Silverscript aims at making the covenant primitives introduced after Toccata in Kaspa usable and readable.
- Developers can write their covenants using a CashScript-like language and compile their contracts to a locking script, ABI, and covenant plumbing code.
Language features
Kaspa Silverscript features the following lines of code;
- Loops and arrays
- Function calls and helper functions
- explicit types, structs, and typed literals
- transaction introspection
- signature checks, hashtags, and verification built-ins
- covenant declarations that generate transition wrappers
What can developers create with Silverscript?
1.) Escrow and milestone payments
2.) Recurring or streaming payments
3.) Vesting and dead-man’s-switch custody
4.) Native fungible assets (KCC20-style conventions)
5.) Atomic swaps
6.) Simple stateful objects such as counters
7.) ZK-aware checks that call the on-chain Groth16 / RISC Zero precompil
If v1 works, Kaspa will have an authorship pathway for L1 covenants that doesn't add a second runtime for audits.
This is less than “Solidity on Kaspa,” but it is the point.
Silverscript is a platform for vaults, assets, and local state contracts and the foundational layer for the future shared state.
Why is everyone suddenly talking about kaspa:native?
Bitcoin accounts with millions of followers. Gemini running livestream segments. BitGo writing native Kaspa support into their code. All in a bear market.
But not all of it is what it looks like. One of these headlines is designed to scare you out of your bag, and one big "JUST IN" is just wrong.
I checked each one directly. What's real, what's noise, and what's a trap, all broken down.
Full video linked below. 👇
Why Is Everyone Suddenly Talking About Kaspa?! - https://t.co/LIL4cKa8Tv