Learn · stop 4 of 5

How it fits together

One story, top of the stack to the bottom: a vault that protects coins even from a thief holding your keys. Every layer you met at the last stop does one job here.

1. 1
   You

   Start with a rule worth enforcing

   "These coins can only be withdrawn after a 24-hour delay, and only to my address — no matter who steals my keys tonight." That sentence is a vault.

2. 2
   Silverscript

   Write the rule as code

   A few dozen lines describing the allowed state changes: old state + your request + the transaction's facts → the new state that's permitted. Nothing else is.

3. 3
   Kaspa Script

   The compiler machines the lock

   Silverscript compiles your rule down to Kaspa Script — the raw covenant the chain understands. You never hand-wire this layer, the compiler does.

4. 4
   Kaspa consensus

   Deposit — the rule becomes physics

   You send coins into the covenant. From this moment the rule isn't a promise or a company policy: every node on the network checks it on every spend attempt.

5. 5
   Kaspa consensus

   A thief tries — and the chain says no

   Someone with your stolen keys broadcasts an instant withdrawal. The spend breaks the delay rule, so consensus rejects the transaction like a coin that doesn't fit the slot. It never happened.

6. 6
   Explorer

   Anyone can verify it

   The covenant, its rules and its history are public. An explorer like kascov.io shows the vault sitting there, enforcing itself, with no company in the loop.

Multi-contract apps follow the same story with one extra chapter: Argent wires several covenants into one application before everything compiles down.