TD:LR 

• R&D emphasized parallel work over linear roadmaps: Kaspa core developer Michael Sutton described ongoing development as a “DAG of efforts,” highlighting parallel progress on programmability (vProgs, covenants, new Script opcodes, ZK verification) and fee-market design aimed at addressing long-term security economics.

• DagKnight advanced toward dynamic-DAG readiness: Kaspa developer coderofstuff shared a technical update on DagKnight (DK), noting that the devnet v0 iteration can now run over a dynamic DAG within simulation tooling, with internal devnet testing planned next.

• Execution-layer infrastructure broadened: Igra advanced community-run infrastructure via Galleon Node v2 (testnet configuration), while K.A.T. signed a Hyperlane integration agreement to support future cross-chain asset access once deployment goes live.

• On-chain applications expanded beyond payments: Kasanova launched wallet-native on-chain messaging tied to KNS identity, while Kasplay showcased Kaspa-native retro games and other lightweight, high-frequency on-chain interactions, including fee comparisons intended to illustrate the practicality of frequent on-chain writes.

• Community visibility grew via public media and in-person events: Blockchain Banter highlighted ecosystem tooling and exchange-listing commentary, while KaspaCom and local organizers promoted participation in Israeli and Dutch community events. 

KASmedia Analytics Charts 

KASmedia has added a new on-chain indicator to its Kaspa analytics library: Net Unrealized Profit/Loss (NUPL), a metric that measures the aggregate unrealized gains or losses held across the network.

Rather than tracking spot price behavior, NUPL evaluates whether the average coin is held at a profit or a loss relative to its last on-chain movement. Across proof-of-work networks, shifts between negative and positive NUPL zones have historically aligned with broader changes in market structure, offering a high-level view of sentiment and positioning without relying on short-term price signals.

Kaspa R&D Activity Reflects Parallel Development Structure

Kaspa community member Manyfest (@manyfest_) summarized recent research and development activity across Kaspa’s open Telegram channels, citing Michael Sutton’s description of current work as DAG of development efforts. The framing echoes Conway’s Law, which holds that system architectures tend to mirror the communication structures of the teams that build them.

The summary highlighted parallel efforts across multiple areas, including improvements to node connectivity, research into fee mechanisms, transaction data retrieval, DagKnight development, vProgs implementation, new Script opcodes for covenants and zero-knowledge verification, native token design paths, a Python SDK, and tooling for direct ASIC-to-node mining.

Responding to the overview, Sutton added: “Nice summary. Tbh, the most exciting recent development is actually still in stealth mode. Soon^tm.”

In a follow-up exchange on security budget and hash rate pressures, Sutton framed the situation as a forcing function accelerating long-term solutions rather than a setback, pointing to two main focus areas: expanding utility and usability through programmability, and designing improved fee markets to decouple fee revenue from constant network saturation. The exchange underscores both the breadth of active experimentation across the Kaspa ecosystem and the decision to tackle structural issues early rather than defer them.

DagKnight: v0 Development Update

Kaspa developer coderofstuff shared a technical update on progress toward DagKnight (DK), focusing on the initial devnet v0 iteration. In an earlier, as-yet-unpublished outline by Michael Sutton, the DagKnight effort is structured into three phases: devnet v0, testnet v1, and a mainnet candidate v2.

The v0 phase is focused on establishing a complete end-to-end execution flow, even if some protocol components are only partially implemented. Since the previous update, several additions have been made, including an efficient k-searching algorithm and the introduction of gray blocks to replace representatives. As coderofstuff explained:

“Since the last update, more things have been implemented, such as an efficient k-searching algorithm and gray blocks (to replace representatives). The most important change since then is that DK can now be run over a dynamic DAG.”

This milestone was enabled through integration with Simpa, a Rusty-Kaspa simulation engine that supports testing under dynamic DAG conditions. A small number of remaining changes are expected to be completed in v0 shortly, after which the DagKnight branch will be cleaned up, merged into the main repository, and deployed to a limited internal devnet for controlled live testing on Kaspa.

Ori Newman Shares Illustrative Covenant Concept Using “Silverscript”

Kaspa developer Ori Newman shared a short code snippet that sparked discussion around covenant-style programmability on UTXO-based systems. While some reactions framed it as demonstrating UTXO splitting on a BlockDAG, the snippet itself appears to be illustrative rather than executable.

According to an analysis by Grok, the example sketches a conceptual “splitting covenant,” summarized as:

“This UTXO can only ever be spent by splitting its value into N equal parts and sending each part to a new pubkey. No other spending is allowed. And N cannot be larger than the max_outs parameter I set when I created this thing.”

The code does not map directly to current Bitcoin or Kaspa implementations and omits the transaction introspection required for real enforcement. It is best understood as a design sketch aligned with Kaspa’s broader exploration of native covenant-based programmability.

Kaspa Ecosystem Integrates Hyperlane for Cross-Chain Asset Access

Kaspa ecosystem project K.A.T. announced that it has signed an integration agreement with Hyperlane, alongside ecosystem partners Igra Labs, AppKaskad, ZealousSwap, and KaspaCom. The agreement establishes Hyperlane as the cross-chain messaging layer for planned bridging into Kaspa’s execution environments.

Hyperlane is a permissionless cross-chain messaging and bridging framework that allows ecosystems to deploy customizable interchain routes rather than relying on a single, monolithic bridge. Instead of enforcing one fixed security model, Hyperlane enables developers to choose how cross-chain messages are verified, making it a flexible infrastructure layer for moving assets and data between blockchains.

According to the announcement, support for assets such as USDC.e, USDT.e, and wETH.e are planned for availability on Igra via Hyperlane-based transfers. The integration is not yet live, and activation is expected to coincide with the deployment of the relevant execution environments, though no specific network stage or timing was specified.

The teams described the agreement as a production-ready infrastructure commitment that lays the groundwork for future cross-chain asset access within the Kaspa ecosystem.

A Community Visualization Exploring Kaspa vProgs

Following the release of the vProgs repository, Kaspa community member Luke Dunshea (@elldeeone) published a fun, interactive visualizer designed to make differences between smart contract execution models easier to understand.

Titled “The Grocery Store Problem,” the visualizer contrasts a single-queue market, representing traditional smart contract platforms such as Ethereum, with a parallel market, representing Kaspa’s proposed vProgs model on Kaspa. As the site explains:

“Traditional smart contracts execute in a single global sequence. Even unrelated transactions wait in the same queue.”

By contrast, the parallel model illustrates how per-resource ordering works in practice:

“Different items → different lanes → no cross-item waiting. Only shoppers grabbing the same item coordinate.”

Using animated shoppers and checkout lanes, the visualizer shows how contention remains local under the parallel model: contracts touching the same state still coordinate, while unrelated transactions continue to execute independently. Users can adjust contention levels and observe both approaches side by side to see how shared state affects throughput.

The project is not intended as a precise technical simulation. Instead, it functions as a fun, lightweight, intuition-building visual aid, emphasizing that vProgs represent a different execution paradigm rather than simply a faster version of existing smart contract systems.

Igra Advances Community-Run Execution Infrastructure With Galleon Node V2

Kaspa execution-layer developer Igra Labs announced the availability of Galleon Node V2 for community node operators, marking a step toward decentralized operation of Igra’s execution environment. While the current release is configured for testnet, the team indicated that mainnet deployment parameters are expected to follow.

The update introduces architectural changes to how execution-layer data is exchanged with Kaspa’s consensus layer, along with improvements to stability during chain reorganizations and node restarts. According to the team, the release allows Igra state to be independently verified and maintained on community hardware, supporting censorship resistance and reducing reliance on centralized infrastructure.

Kasanova Wallet Launches On-Chain Messaging Feature

Kaspa wallet provider Kasanova Wallet announced the public release of an on-chain messaging feature that allows users to exchange messages directly through the Kaspa network. The functionality is integrated into the wallet and uses Kaspa Name Service identities, requiring users to mint and set a primary KNS domain before initiating conversations.

According to the team, the feature is designed to enable decentralized, wallet-native communication without reliance on off-chain messaging infrastructure. The launch expands Kasanova’s feature set beyond asset management, positioning the wallet as an interface for both financial activity and identity-linked interaction within the Kaspa ecosystem.

Kaspa Commentary on Layer-2 Fragmentation

The @KaspaGLOBAL X account outlined its critique of Layer-2 scaling architectures, arguing that rollups and similar systems introduce fragmentation rather than resolving base-layer limitations. The post uses the metaphor of “a hotel with no hallways” to describe Layer-2 networks as isolated execution environments:

“Think of them as individual rooms in a hotel that has no hallways. They are fast, but your money gets trapped inside each room.”

Kaspa highlighted cross-chain and inter-rollup bridges as a persistent security risk, noting that asset movement between these environments requires external coordination outside the base security layer:

“To move between them, you have to exit the building and use a risky bridge.”

“Bridges are a primary source of hacks because they sit outside the main security layer and require coordination between trusted parties.”

The post contrasts this model with Kaspa’s stated design goal of maintaining scalability, assets, and execution directly on the base layer. Rather than connecting fragmented systems, Kaspa argues that fragmentation itself should be avoided:

“For Kaspa, the lesson is clear: do not connect fragments. Avoid creating them.”

“If an app has to leave the base layer to scale, the architecture has failed its mission.”

Kaspa framed its alternative as a unified base-layer system secured directly by proof-of-work consensus:

“We are building a unified system where all assets stay in one environment protected by thousands of independent mining units.”

“Unity always beats fragmentation.”

Kaspa Proposed as Payment Layer for Autonomous AI Agents

Kaspa developer Alex Apichukov highlighted a potential role for Kaspa as a machine-to-machine payment network, as interest grows around autonomous AI agents that operate continuously, coordinate with other agents, and pay for tools or APIs without human involvement. Apichukov pointed to Kaspa’s sub-second confirmations, high throughput, and low fees as properties suited to AI-to-AI transactions, and shared a Kaspa MCP server that enables agents to generate native KAS wallets and execute transactions programmatically. A Kaspa MCP (Model Context Protocol) server is an interface layer that lets AI agents interact with the Kaspa network programmatically.

The discussion builds on broader interest in autonomous agent frameworks, including projects such as OpenClaw, which highlight how always-on AI agents may require native, low-latency payment rails to transact programmatically around the clock.

The idea was echoed by community member CyberVisualizer, who framed a stack combining Moltbot, Moltbook, and Kaspa as a potential long-term foundation for autonomous agent coordination, stating:

“Moltbot + Moltbook + Kaspa = Endgame.”

In this framing, Moltbot functions as an autonomous agent capable of executing tasks and workflows, while Moltbook provides the structured context or knowledge layer those agents operate within. Kaspa serves as the settlement and payment rail, allowing agents to transfer value, pay for services, or coordinate economically in real time. Contributors emphasized that these integrations remain experimental and are still in early testing stages.

Kaspa-Native Retro Games and On-Chain Arcades

Kaspa community developer feciuszek (@feciuszek) launched Kasplay.fun, a Kaspa-native retro gaming site that records gameplay activity directly on the Kaspa BlockDAG. The project is positioned as a lightweight on-chain arcade and technical showcase rather than a commercial gaming platform.

Games on the site include:

• Tetris – classic puzzle stacking

• Snake – grows by eating crypto.

• Breakout – brick-breaking action

• Invaders – defend Kaspa

• Kaspac – eat crypto coins (PacMan)

• KasBomber – bomb the cryptos.

• KasRacers – race with crypto cars

• Kas Rocket – to the moon challenge

• BlockDAG – run through the DAG.

• KasMiner – GPU mining pinball

• KasRunner – jump over legacy systems.

• Crypto Shooter – pop crypto bubbles

• Trilemma Quest – blockchain learning game

• Snake Arena – multiplayer PvP rounds on Kaspa BlockDAG

Feciuszek described the project’s origins as personal and experimental:

“I built Kasplay mainly for my kids, so they can use Kaspa instead of Roblox 😅

It’s awesome to see others enjoying it too.”

He emphasized that Kasplay is currently non-monetized and intended as a hobby project:

“Right now Kasplay is just a fun, free on-chain arcade and a tech showcase for Kaspa — no monetization, no ads, no entry fees.”

While users have suggested reward-based gameplay, he noted that incentives would require external support:

“If at some point there is a sponsor or a clear reward pool, I’d be happy to integrate real prizes.”

As of January 28, Kasplay reported that more than 9,700 games had been played and recorded on Kaspa’s BlockDAG. On January 30, the Kasplay team announced new anti-spam and anti-abuse protections aimed at improving leaderboard integrity, noting that the changes enable future weekly challenges and potential rewards.

The project highlights Kaspa’s suitability for lightweight, high-frequency on-chain interactions by using simple games to demonstrate throughput, ordering, and user-level engagement without introducing fees or complex incentives.

While Kasplay.fun currently offers the widest selection of on-chain games, other Kaspa community projects are also exploring retro gameplay formats. TX Missile Command adapts the classic missile-defense arcade game into a Kaspa-themed implementation, while Kaspa Pong offers a minimalist Pong-style experience focused on responsiveness and simplicity. Together, these projects highlight growing experimentation with lightweight, high-frequency interactions on Kaspa.

Kaspa Details Block Processing Pipeline Architecture

A new explainer published on Kaspa.com by Kaspa Facts outlines how Kaspa validates and integrates blocks using a four-stage block processing pipeline designed for a BlockDAG environment. The architecture separates block handling into sequential phases—header checks, transaction validation, virtual state computation, and pruning—allowing multiple blocks to be processed in parallel while preserving correct dependency ordering.

The post explains that Kaspa’s pipeline addresses challenges unique to DAG-based systems, where blocks may arrive out of order and reference parents that have not yet been processed. A dependency manager coordinates parent–child relationships to ensure blocks advance only when prerequisite data is available, while message queues and dedicated processing threads allow concurrent execution without compromising state consistency. According to the article, this design enables Kaspa to sustain high block rates, maintain bounded storage through pruning, and provide a stable virtual state for wallets and miners.

Kaspa as Energy Grid Sequencer

Electrical engineer Honorius @OrangutanElder frames Kaspa as a "permissionless switchboard for ordering and finalizing digital commitments" – the neutral sequencing layer complex physical systems like energy grids have lacked since telecom built the modern Internet.

Physical energy flows cannot be routed like data packets, but the digital commitments governing generation, storage, and discharge absolutely can. Honorius lays out a model in which decision logic and control rules operate off-chain, while Kaspa provides the stateless sequencer beneath it, ordering and finalizing commitment proofs via vProgs and DAGKnight to guarantee verifiable integrity and settlement without centralized trust.

"Energy is GDP now that compute is the new marginal producer of output," he notes, making a shared digital control plane economically critical. Legacy grids remain "dumb" without it—stuck coordinating supply, demand, and storage through inefficient analog models. Kaspa changes the game as the neutral base layer.

Blockchain Banter Space Highlights: Kaspa Ecosystem, KasMap, and Market Structure

In a recent Blockchain Banter livestream, hosts J (QuickCrypto) and Ger (Crypto Pumpz) were joined by Seb, creator of KasMap, and Wolfie, Kaspa’s unofficial business development officer, for a detailed discussion on Kaspa’s ecosystem tooling, exchange listings, and long-term protocol direction. The discussion focused on exchange mechanics, ecosystem tooling, and protocol design, with participants repeatedly returning to Kaspa’s core thesis as “the next logical progression of Bitcoin in leaps and orders of magnitude.”

​A central focus of the conversation was Kaspa’s status with large centralized exchanges, including Binance, OKX, and Coinbase. Speakers indicated that much of the required technical integration work on Kaspa’s side has been completed for some time, with listing activation remaining an exchange-level decision shaped by internal priorities, market conditions, and regulatory considerations.

In reference to Binance, Wolfie stated:

​“We finished it two Christmases ago. They could flick spot trading on — it’s that simple. We’ve been ready for them for over two years.”

Despite the frustration with the exchange listing delays, the discussion then turned to highlight the growing pipeline of on-chain activity, including execution layers, messaging applications, and potential prediction markets, as usage that could drive renewed institutional interest, while noting that no formal timelines or commitments were disclosed.

Seb then described KasMap as a grassroots adoption tool focused on merchant onboarding and community coordination. He outlined how the platform combines a global user map, merchant directory, events listings, and a marketing hub to support organized adoption efforts.

He emphasized: ​“We are not a company — we are a decentralized community. Everybody who likes Kaspa and wants to see Kaspa succeed has a role to play in that.”

He further described coordination at scale, particularly through global merchant onboarding, as a way to translate individual participation into measurable outcomes:

​“If you do it alone, it feels like you’re not making any dent. But if we say globally we want to onboard a thousand merchants, suddenly it becomes actionable.”

On the protocol side, speakers discussed Kaspa’s long-term technical objectives, emphasizing capabilities that extend beyond near-term market considerations. Seb described real-time decentralization (RTD) as a foundational design goal tied to latency, throughput, and responsiveness:

​“Real-time decentralization is really the perfect end goal of crypto — instant reaction without latency. That has never been possible before.”

The discussion framed progress primarily in terms of delivered infrastructure and ecosystem readiness, including RTD, vProgs, and execution layers, rather than short-term price movements.

KaspaCom to Attend Israeli Crypto Forum Event

KaspaCom will attend a closed special event hosted by the Crypto Companies Forum in Tel Aviv-Yafo on Tuesday, February 3, from 9:30 AM to 12:00 PM GMT+2..

The event brings together Israeli Web3 companies, venture firms, infrastructure providers, and policymakers to discuss the regulatory and institutional outlook for crypto and digital assets in Israel. Topics include potential stablecoin legislation, token issuance frameworks, equity tokenization, and broader efforts to enable compliant crypto activity within the country.

Organizers plan to present new research on crypto adoption in Israel alongside a coordinated campaign to advance crypto and Bitcoin reform across the political spectrum. The program includes executive panels and strategy sessions focused on influencing policy outcomes and expanding real-world adoption.

Confirmed speakers include Adam Benayoun (Collider VC), Oren Katz (Starkware COO), Idan Efrat (Fireblocks), Yuval Roash (Bits of Gold CEO), Ben Samocha (CryptoJungle CEO), Tzachi Iron (Psagot Investments CEO), Shauli Reguan (Masterkey VC), Nir Hirschman (Forum CEO), and Lior Meiri (campaign creative lead).

KaspaCom’s presence underscores ongoing work to boost Kaspa’s institutional profile amid evolving global regs.

First Kaspa Meetup Announced in the Netherlands

Kaspa community member Olaf Weller has announced the first-ever Kaspa meetup in the Netherlands, set for Saturday, February 7, in Utrecht from 13:00 to 17:00.

This informal gathering welcomes all Kaspians—whether to meet others, swap experiences, or dive into talks on Kaspa’s technology, ecosystem projects, and network updates. The afternoon includes English-language presentations, coffee/tea/water, and optional post-event dinner/drinks. No project or speaking slot required to attend.

Program:

• 13:00-13:30: Welcome

• 13:30-14:00: Olaf Weller on Kaspa Nederland

• 14:00-14:30: TheVisualAye on "The Ledger and the Lily: Authorship and Permanence on Kaspa"

• 14:45-15:15: Seb on KasMap

• 15:15-16:00: Paul van Son on KII (Kaspa Industrial Initiative)

• 16:00-17:00: Drinks

Spots are limited. Secure yours by sending €23 in Kaspa to olafweller.kas or kaspanederland.kas (pay here), then notify Olaf Weller (@WellerOlaf on X), Seb (@BockTor on TG), or bocktor_42479 on Discord.