Blog
DAGKnight Branch Gets Its First Merge Since September
The dagknight branch of Kaspa's Rust node, rusty-kaspa, received its first merge since September on 16 November 2026. Pull request #1168 tidies and prepares the code DAGKnight uses to sort blocks, and a second change that decides close contests, #1172, is still open. DAGKnight is not on mainnet and has no activation date.
What landed: PR #1168
PR #1168, titled "[DK] DK store rename and BFS coloring semantics", was opened by Kaspa developer coderofstuff on 11 November and merged into the dagknight branch on 16 November. It has 7 commits and passed all 8 automated checks.
It makes three changes:
- A clearer name. The storage component called
DagknightStoreis renamedConflictZoneColoringStore, which describes what it holds and lets other code reuse it. - Its own data type. DAGKnight's coloring data now has a separate structure,
ColoringData, copied from GHOSTDAG's. The commit notes say this makes room for new fields and does not change how the protocol behaves. - Back to whole-zone coloring. The branch had been coloring blocks group by group. #1168 returns to coloring the full "conflict zone" in one bottom-up pass, to prepare for planned work on shortcuts.
What "coloring" means
When blocks are mined at the same time, a blockDAG has to decide which ones belong to the honest, well-connected part of the network. Kaspa's protocols do this by "coloring" blocks: blocks inside the best-connected group count as blue, and blocks outside it, such as an attacker's secret chain, count as red.
DAGKnight does this coloring inside a conflict zone, the part of the DAG where competing groups of blocks overlap. Changing how the zone is filled in is groundwork: it sets up the faster "shortcut" calculations that come next. Our parameterless consensus explainer covers the idea step by step.
What's still open: PR #1172
According to the Kaspa account's post, a second change, #1172 by Max143672, is still open. It sets how DAGKnight picks a winner when two groups of blocks are closely matched, the protocol's tie-breaking rule. Tie-breaking went into code review earlier this year, and it needs to be settled before DAGKnight can move towards a testnet.
What this does and doesn't mean
- It's progress. After a quiet couple of months, code is moving on the branch again.
- It's preparation. #1168 sets up later work; it doesn't complete DAGKnight.
- Nothing changes for users yet. Kaspa mainnet still runs GHOSTDAG. There's no testnet or mainnet date, so treat any claimed launch date with caution.
Track every milestone on our DAGKnight status update and the Kaspa upgrade tracker.
Frequently asked questions
Is DAGKnight live on Kaspa?
No. Kaspa mainnet runs GHOSTDAG. DAGKnight is still being built on a separate branch of rusty-kaspa.
When will DAGKnight activate?
No activation date has been announced. It is expected to run on a public testnet before any mainnet hard fork.
Who wrote PR #1168?
Kaspa developer coderofstuff, who opened it on 11 November and merged it on 16 November 2026.
Do I need to do anything with my KAS?
No. Code merged on a development branch doesn't affect coins or wallets. See what DAGKnight changes for holders.
Not financial advice. This article is for education only. dagknight.com is a community project and is not affiliated with the Kaspa Foundation. Details are taken from the pull request and Kaspa's post as of 18 November 2026.