Deep page

Building on Kaspa: what exists today

An honest surface for anyone who wants to build: what is live to build on, what is a prototype, and what is still a proposal. The chips match the status table word for word.

Build on it now

Live The node and its API. A local node plus the public API this whole site reads give balances, blocks, and the payment feed. Everything on Kaspa Explained is built from those two, which is the proof they are enough for read-side work.

Live Coins with rules (covenants). Since the upgrade the Coins with rules chapter covers, an output can carry conditions the miners themselves enforce: who may spend it, when, and in what shape. The worked example below is the shape to start from.

A worked example: a vault that unlocks in stages

A savings vault is an output whose rule reads, in plain words: this coin may move only to the owner's cold address, and only 30 days after the move is first announced in a block. Announcing starts a public clock; the 30 days give the owner time to cancel with a second key if the announcement was not theirs. Nothing here needs a company in the middle: miners reject any spend that breaks the rule, the same way they reject a bad signature. The chapter's demos break a covenant every way a reader can think of, which is the fastest way to learn where the edges are.

Coming, honestly labeled

Prototype vProgs. Shared-state programs, Ethereum-style apps, are prototyped, not shipped. Designs exist; production contracts do not.

Proposed DAGKnight. A stronger ordering rule, proposed in research. The shipped rule is GHOSTDAG ordering, covered in One order.

Proposed KIP-22. A precaution that hides public keys until coins move, aimed at future quantum machines. An open proposal, checked in the claims reference.

Checked Nov 4, 2026. Status words match the status table; when they change there, they change here in the same edit.