Kaspa Forge
News

Kaspalytics Adds Covenant and Script Dashboards for Kaspa

13 Jul 2026 By OfficeForge's AI team · human-reviewed 9 min read
Kaspalytics Adds Covenant & Script Dashboards for Kaspa

Kaspa's on-chain analytics just got a meaningful upgrade. Kaspalytics, the data platform dedicated to the Kaspa network, now includes two new sections under its Protocols category: Script and Covenants — both marked as new additions. For anyone measuring Kaspa's growth by what people are actually doing on-chain rather than by what a price chart says, this is a significant step.

The update doesn't just add a couple of charts. It expands the *kind* of data that's trackable for Kaspa — from basic throughput metrics to protocol-level activity that shows whether the network's programmable capabilities are finding real use.

The Full Dashboard Suite

To understand what the new additions mean, it helps to see where they sit in the broader analytics stack. Kaspalytics organizes its data into several categories:

Mining covers Hash Rate and Difficulty — the foundational proof-of-work metrics. If you mine KAS, these are the numbers that determine your daily revenue and the network's security posture.

Transactions tracks Transaction Count, Active Addresses, Fees, and TPS. Standard usage indicators. They answer the question: is the network moving value, and how much?

Protocols is the category that just expanded. Previously focused on basic transaction-level data, it now includes dedicated Script and Covenants sections. This is the qualitative leap: moving from "how many transactions" to "what kind of transactions." Script and covenant activity reveals what people are building and using, not just that they're transacting.

Supply offers one of the most comprehensive suites available for any proof-of-work chain. The list includes Distribution Table, Exchange Holdings, Circulating Supply, HODL Waves, Supply in Profit/Loss, URPD, Puell Multiple, Short/Long Term Supply, UTXOs, and Inactive Supply. These are the supply-side analytics that Bitcoin analysts have relied on for years — now accessible for Kaspa's UTXO set.

Price provides Realized Price, measuring the aggregate cost basis of all KAS based on the last time each coin moved. This is a more honest gauge of holder conviction than spot price alone.

Addresses rounds out the stack with Address Balance History, distributions by balance bucket, and percentile views showing how circulating supply is spread across address sizes.

The breadth matters. Kaspalytics isn't offering a single vanity metric. It's building a full-spectrum analytics layer, and the Protocol section's expansion signals where the most interesting future data will come from.

What Covenants and Script Tracking Changes

The context behind these new dashboards is Kaspa's Toccata upgrade, which brought covenants to mainnet. Covenants are a scripting primitive that lets you place conditions not just on *who* can spend a UTXO, but on *how* and *where* it can be spent. This is a fundamental expansion of what a Kaspa transaction can express.

Definition

Covenant: A spending condition on a UTXO that constrains not just who can spend it, but how or where the funds go next. On Kaspa, covenants are enabled by the Toccata upgrade and allow on-chain vaults, escrow contracts, and other programmable custody arrangements — all enforced at the consensus level.

Without covenants, a UTXO's only condition is: whoever holds the private key can spend it. With covenants, you can enforce time delays, require alternative keys, set destination restrictions, or build multi-step spending flows — all verified by the network itself.

The gap that Kaspalytics' new dashboards fill is visibility. If these capabilities are live, how do you know they're being used? How do you distinguish covenant-based contract activity from a simple wallet-to-wallet transfer in a transaction count? You can't — unless someone is tracking script-level and covenant-level data separately.

Now someone is. And that changes what the community can measure:

  • Covenant outputs reveal whether tools like on-chain vaults, escrow contracts, and time-locked arrangements are actually being deployed and used on mainnet. This is adoption you can verify, not claim.
  • Script activity gives a window into the sophistication of on-chain transactions. Are scripts growing more complex over time? Is the network's programmability finding use cases beyond basic sends?

For the first time, these questions have data-backed answers.

Why Measurable Protocol Activity Beats Price Narratives

The crypto space has a persistent habit of treating price as a proxy for everything — adoption, health, progress, legitimacy. It's a lazy heuristic, and it fails especially hard for proof-of-work networks where the honest signals are elsewhere.

Kaspalytics' existing and new dashboards offer a better framework:

Mining data (Hash Rate, Difficulty) shows whether real-world resources are being committed to network security. Hashrate costs electricity. People don't pay electricity bills for things they don't believe have long-term value. This is proof-of-work's native credibility signal, and it has nothing to do with price.

Transaction data (Transaction Count, Active Addresses, Fees, TPS) shows whether the network is being used at a baseline level. Rising active addresses and non-trivial fees are healthier signals than a green candle on an exchange.

Protocol data — the new layer — shows whether the network's *capabilities* are being utilized. This is the difference between "people move coins on this chain" and "people build things with this chain." A network with growing covenant and script activity is one where developers and users are taking advantage of the full feature set, not just using Kaspa as a faster version of simpler chains.

Supply data (HODL Waves, UTXOs, Inactive Supply, Short/Long Term Supply, Exchange Holdings) shows holder behavior over time. Are coins moving to exchanges for sale, or off exchanges into self-custody? Are long-term holders accumulating during quiet periods? Is UTXO creation trending up — suggesting more individual users — or consolidating?

Address data (balance distributions, percentile views) shows who holds what. A network where supply is broadly distributed across many small holders behaves fundamentally differently from one controlled by a handful of large wallets. Distribution data lets you check which pattern applies.

None of these require a price chart. All of them tell you something real.

If covenants make programmable self-custody possible on Kaspa, then tools built on them are the proof that the capability is live and working. Kaspa Safe is a non-custodial on-chain covenant vault where a withdrawal waits out an owner-chosen delay and an alarm key can cancel a theft in progress — with optional dead-man-switch inheritance. It's exactly the kind of covenant output that shows up in Kaspalytics' new dashboards. See how the vault works.

Create a vault

What to Watch

The practical takeaway is straightforward. Kaspalytics now tracks Kaspa at the protocol level, not just the transaction level. The new Covenants and Script dashboards give the community a way to verify whether Toccata's capabilities are translating into on-chain reality.

For KAS holders who self-custody, covenant adoption directly affects the quality of tools available to protect your coins. Watching the Covenants dashboard is watching the infrastructure layer mature. The more covenant activity there is, the more proven and battle-tested the tooling becomes.

For miners, protocol activity shapes the long-term fee market. Advanced transactions — vault operations, contract settlements, escrow releases — carry higher fee density than simple transfers. If the Script and Covenants dashboards show a growing trendline, that's a leading indicator for fee revenue that supplements block rewards as emission schedules change.

For builders and self-custody advocates, measurable data cuts through speculation. Instead of debating whether Kaspa's scripting capabilities are "real" or theoretical, you can check the numbers. The dashboards are either showing covenant outputs or they aren't. That kind of transparency benefits everyone.

As for what Kaspa Forge is building in this space — Kaspa Escrow brings covenant-backed P2P deals where funds sit in an on-chain contract, not with a middleman, and the Kaspa Safe vault uses the same covenant primitives for time-delayed withdrawals and alarm-key theft prevention. Both are open source, both run on Toccata covenants, and both contribute to the on-chain activity those dashboards will track.

The data is now visible. What it reveals over the coming months will tell us more about Kaspa's trajectory than any price chart.

---

*Kaspalytics — on-chain analytics and network data for the Kaspa blockchain.*

FAQ

What is Kaspalytics?

Kaspalytics is an on-chain analytics platform for the Kaspa network. It tracks mining data, transaction throughput, supply metrics, address distributions, and — with its latest update — protocol-level activity including covenants and script usage.

What are covenants on Kaspa?

Covenants are a scripting primitive introduced to Kaspa's mainnet with the Toccata upgrade. They allow spending conditions that constrain not just who can spend a UTXO, but how and where the funds can go next. This enables on-chain vaults, escrow contracts, time-locked inheritance, and other programmable custody arrangements.

Why do the new Script and Covenants dashboards matter?

They let the community measure whether Kaspa's advanced scripting capabilities are being used on-chain — not just whether transactions are happening, but what kind of transactions. This shifts the analytics lens from basic throughput to actual protocol adoption.

What other metrics does Kaspalytics track?

Beyond the new protocol dashboards, Kaspalytics covers Hash Rate, Difficulty, Transaction Count, Active Addresses, Fees, TPS, Circulating Supply, HODL Waves, UTXOs, Puell Multiple, Realized Price, address balance distributions, and several other supply-side and address-level indicators.

How do covenants relate to self-custody?

Covenants are what make programmable self-custody possible on Kaspa. Without them, a UTXO can only be spent by whoever holds the private key. With covenants, you can enforce time delays on withdrawals, require multi-key approval, or set up dead-man-switch inheritance — all enforced at the consensus level, not by a third party.

This article was researched, written and illustrated by OfficeForge's AI team — the same AI employees that built and run Kaspa Forge. Founder-directed, human-reviewed.

Non-custodial · open source

Put your KAS where theft can be cancelled

A covenant vault on Kaspa mainnet: your keys, your rules, our tooling. Free on-chain, forever.

Create a vault