The funding edge

You don't need KAS.

You need an agent that cannot overspend. Sell what you already hold, once. What arrives becomes authority the network enforces — and every payment after that is a rule nobody can route around.

USDC or USDT, or anything with a market sold once, at a rate you choose KAS one coin, at your own key genesis above — somebody's word below — refused by the network the grant a coin locked by a script budget 3 KAS, for its whole life per payment 0.25 KAS payees fixed at creation expires block 598641927 hundreds of payments sub-cent fees · each one refused if it breaks a rule the conversion happened once; this happens all day
above the line

Somebody's word

An exchange sold you KAS. A rate was what it was. Warda saw none of it, is not party to it, and says so on the receipt — it holds no key and takes no custody at any point on this path.

below the line

Refused by the network

The budget, the per-payment cap, the epoch limit, the window and the payee list are conditions in the script that unlocks the coin. A payment that breaks one is not rejected — there is no such transaction to submit.

The part most people get wrong

The limits are in KAS, and they have to be.

It would read better as $100 budget, $5 per payment. It cannot be built. A covenant is a script validated by Kaspa consensus, and consensus compares sompi because that is what it can see — there is no price on L1 and no oracle to ask. A covenant that trusted a signed price would have moved the limit back into a process that can be wrong or captured, which is the arrangement this whole protocol exists to argue against.

So dollars live at the edges, where they belong. You think in dollars when you fund. A seller may price in dollars and the quote converts at the moment of payment. The cap in the coin stays in KAS, and if a rate move pushes a dollar-priced service over it, the payment refuses. That is the covenant working, not a gap in it.

What that buys you: every limit on this page can be checked by a stranger against the chain, with no account and nothing of ours in the way. A dollar limit could only ever be checked against our word.

Not a diagram

Agent #006 was funded this way, and has already spent.

Every figure below is a transaction. The agent was bought rather than hand-funded, its three powers are held by three different keys, and it has paid a vendor under the limits above.

grant
kaspatest:ppcf3e34glskreft0ls8v7fxxudj8n52ua86dd7t3c83wyn5f83h6hd4yes97
created by
4ae57de08eaa800d63496f4d119014b1c753b588f1b8f1e0626caf6198b07a89
first payment
c8e2b9f990351fb0863303c2089bf37bf11f447984872395a7a6c5be48f489ac
spends
agent key — within 3 KAS, 0.25 a payment, 2 an epoch
stops it
a separate revocation key, which receives nothing
receives
the principal, on revoke or at expiry

The funding itself is recorded too — which asset, which venue, the rate and whose word it is — because that is the one part of this nobody can re-derive from the chain later. It is the only thing on the page marked assumed, and it is marked that deliberately.

Do it yourself

Two commands, and one of them is you selling something.

warda fund --payees payees.txt --budget 3 --max-per-spend 0.25 \
  --rate 0.05 --asset USDC --venue "wherever you trade" --wait

It works out what to sell, tells you where to send the KAS, waits for it, and bounds what arrives. The rate is yours: Warda does not fetch prices, because a price this tool went and got would be a number we vouch for, and the receipt would carry our name where yours belongs.

Start here · watch the agents · how the covenant works