Set a periodic budget

Cap an agent's cumulative spending over a recurring time window, tracked by Kaspa consensus time.

#When to use this

Use a periodic budget whenever you want to cap total spending over time — a monthly allowance for a recurring-bill-paying agent, a weekly cap for an automated purchasing bot — independent of the per-transaction limit, which only bounds a single spend.

#Steps

1. Decide the budget amount and the period length. Period length is expressed in the covenant's native consensus-time unit (DAA score), not wall-clock days — the dashboard and SDK convert a human period (for example, "30 days") into the correct DAA-score length for you.
2. From the vault's (or agent's) policy configuration, set the periodic budget amount and period length.
3. Review and sign. This is an owner-signed covenant operation.

#How rollover works

The covenant rolls the period over automatically once the network's DAA score has genuinely advanced past the committed period boundary — see Periodic budget for exactly why this cannot be faked by an agent claiming an early reset. You do not need to manually reset anything; the next spend after a period boundary is evaluated against a fresh budget.

#Combining with a per-transaction limit

A periodic budget and a per-transaction limit are independent and both apply — set both if you want to bound both a single spend's size and the cumulative total over time.

#Verifying it

Simulate a spend that would exceed the remaining budget for the current period and confirm it is refused with a clear reason (see Budget exceeded) before relying on it.

See also: Periodic budget.