Agent #002

—

The question this answers

Who can change what an agent may spend, and how fast?

Agent #001 answers how much and to whom. The harder question is the one people ask second: fine, but who edits that policy, and how long does it take to take effect? On most systems the answer is whoever holds the config, immediately — which means the limits are a description of intent, not a constraint.

A Warda grant’s terms cannot be changed once it exists. Not by the agent, not by the operator, not by the principal, not by all of them together. The only way to give an agent different authority is to issue a different grant. So the real question becomes how fast a new grant can start — and that is a number the network enforces.

—

created may first spend

There is no timelock mechanism in any of this. The covenant already checks claimedDaa >= notBefore on every spend, so the delay is enforced by consensus rather than by a contract somebody could upgrade to skip it. And because a grant’s address is a hash of its terms, pending authority is publishable the moment it is created: anyone can read what it will permit and check that it cannot yet permit anything.

Who it pays

The addresses it may pay

A name over an address is a claim about identity, and an ordinary address makes it unfalsifiable — it is whoever we say it is. So each name below is re-derived on every run from a published artefact, and one that stops matching is dropped: the address is then shown without a name, which is worse to read and far better than a name that is wrong.

Both ends of this are ours

Agent #001 and agent #002 were both built here. This is therefore not a market, and saying otherwise would be the easiest claim on this site to catch out.

What it is: a payment between two independent grants, with two different keys, each able to pay exactly one address, settled on a public chain where anyone can look it up. The demonstration is that the rails work between agents — not that a third party chose to trade with us.

The digest #002 pays for is also published free at wardaprotocol.com/agent-001.json. Paywalling it to make this look better would have swapped the one claim here a stranger can verify for one that merely sounds impressive.

Its authority

What it is allowed to do

Budget—

Spent—

Remaining—

Max / payment—

Per epoch—

Authorized payees—

May not spend before—

Held on chain—

Its limits

What it cannot do

Every sentence below is produced by running the same function the payer runs before it builds a transaction — against this grant, with these numbers. None of them is copy. If the grant’s limits changed, these would change with them, or the page would not build.

Its work

Every attempt it has made

Refusals included. A purchase log that records only the successes is a sales brochure, and the run that was turned away for being early is the more interesting half of this one.

Attempts—

Served—

Settled on chain—

Outside the allowlist0 KAS

What the agent says it did

What the chain says arrived

Coins at this grant’s payees that one of the receipts above names. Attribution is by transaction id, not by address — a payee’s address serves whoever pays it, and more than one agent here pays the same one, so “it arrived after this grant opened and is under its cap” is a guess rather than a fact.

Honesty

What this does and does not protect you from

The network enforces

It can pay agent #001 and nobody else
It could not pay anything before its start time
No single payment above the cap
No more than the budget, ever
Its terms cannot be edited — only replaced, by a new grant

Nothing here promises

That the digest is correct
That the seller delivers what it charged for
That a payment is refundable
That the two agents are strangers — they are not
That testnet coins are worth anything

Agent #001’s second grant paid a third-party vendor 1.47 KAS for a service that never arrived. That is on its page, with the transaction id, for the same reason this column is here: the covenant bounds what a vendor who takes payment without delivering can take, and it does not do anything else.

Check it

The dashboard is not the source of truth

Every field below is on the chain. Nothing here needs to be believed.

Agent ID—

Network—

Grant address—

Agent key—

Principal—

Covenant ID—

Buys from—

Reproduce the purchase yourself:

BASH

git clone https://github.com/ArtyKOMarkets/warda && cd warda/agent-002
source ../ops/node.env
WARDA_SK=$(cat ../covenant/deploy/agent-002.key) \
  node --experimental-strip-types tools/buy.ts \
  https://warda-demo-api.vercel.app/digest

The key is not in the repository, so that command will pay from your grant, not ours. agent-002/README.md has the three commands that mint one.