DagLock · Kaspa L1 · Beta

Locks that enforce themselves.

Vesting the network enforces — not an admin key. Deposit, set a schedule, and Kaspa releases it over time. No pause button. No backdoor. Proven live on mainnet.

Covenant-enforced Non-custodial Mainnet-proven
A first on Kaspa

Locks that enforce themselves.

DagLock is a covenant — a lock written into Kaspa itself. Deposit tokens, set a schedule, and the network releases them over time. No pause button. No backdoor.

The idea

Deposit. Set a schedule.
Walk away.

Team allocations, grants, treasury — locked on a timeline anyone can see. Once created, nobody can accelerate it or pull it early. Not the team. Not us.

Why it's trustless

The network holds it.

Every Kaspa node runs the rule: only the beneficiary can claim, only what has vested, and the rest is forced back into the same lock. Spend conditions in consensus — not a contract someone owns.

Step 1 — Create

Create a lock.

Pick an amount and a schedule. DagLock shows you the exact terms, then you confirm.

2 KAS · 5-min cliff · four steps · fully vested in 20 min

/new 2 5 5 4
LOCK PREVIEW
total 2 KAS = 4 × 0.5
cliff in 5 min · ends in 20 min
➡️ /confirm to broadcast
/confirm
✅ BROADCAST · lock created on mainnet
Step 2 — Verify

Anyone can verify it.

The badge proves the on-chain script is a genuine DagLock and that it's funded to exactly what it claims — by matching a published fingerprint. One wrong byte, no badge.

verified   funded
c8e2b568…611e33d9
Step 3 — Vest

It vests over time.

Time comes from the block clock, so it can't be faked forward. As each period passes, a slice becomes claimable — and everything still locked stays untouchable.

Step 4 — Claim

Claim what's vested.
The rest stays locked.

Take the vested slice; the covenant forces the remainder back into the identical lock, same lineage. Repeat until fully vested, then the final claim closes it.

partial → 0.5 out · 1.5 re-locked  •  final → lock closes

Proven, on-chain

Live on Kaspa mainnet.

The full lifecycle — create, vest, claim, close — ran on mainnet with real KAS. Audited, red-teamed, and checked against the real Kaspa script engine.

create2498f0fd…
partial claimb2e3eb9d…
final claim20df88ef…
resultevery sompi accounted for
01 — What it is00:00
How it works

Enforced by Kaspa. Owned by no one.

No admin key

A DagLock isn't a contract someone owns — it's a spend condition every node enforces. There is no pause, no override, no early exit for anyone.

Vested-only claims

Only the beneficiary can claim, and only what has vested. The unvested remainder is forced back into the identical lock on every claim — provable by its on-chain lineage.

Verify it yourself

The badge matches the on-chain script against a published fingerprint and checks it's funded to exactly what it claims. Don't trust us — check the chain.

Status
● KAS locks — live & mainnet-proven ◆ Token locks + launch badges — next

Lock your project's token with a verifiable 🔒 badge on every launch — landing in Dagger. Join the community to get it first.

Beta software, not yet externally audited. Locks are enforced by Kaspa consensus; always verify a lock's fingerprint, beneficiary, and terms yourself before relying on it. Nothing here is financial advice.