testnet
—
—
—
—
—
Authority
Activity
—
These are not settings. They are in the script that unlocks the coin, and the network checks them on every spend — including the one that is crossed out.
The question this answers
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
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.
Its lineage
A Warda grant’s terms cannot be edited. Replacing what an agent may spend therefore means ending one grant and starting another — and the grant that ends does not get a say in it, because the key that ends it is not the agent’s.
Its lineage
This grant was not issued by a person. Another grant subdivided itself and handed over a bounded piece of its own authority — which the covenant permits only in one direction. Each figure below is parent → child.
Its authority
Its limits
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
Refusals included. A purchase log that records only the successes is a sales brochure.
Honesty
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
Every field below is on the chain. Nothing here needs to be believed.
Reproduce the purchase yourself:
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.