The console for whoever
gives the agent money.

Install it

1. Check what you downloaded. The hash above is generated from the file itself when this page is built, so the two cannot disagree.

   shasum -a 256 wardaprotocolconsole-0.1.0-chrome.zip

2. Unzip it somewhere you will not delete by accident. Loading an unpacked extension points the browser at that folder and keeps pointing at it.
3. Open the extensions page — brave://extensions, or chrome://extensions — and turn on Developer mode.
4. Load unpacked, and choose the unzipped folder — the one with manifest.json in it.

Your browser will remind you on every launch that a developer-mode extension is installed. That warning is correct and will go away when this is on the store. It does not auto-update, so a new version means doing this again.

Or build it

Same result, nothing to trust.

git clone https://github.com/ArtyKOMarkets/warda
cd warda && npm install
npm run build --workspace @warda_protocol/console
# load extension/build/chrome-mv3

The first five minutes

1. Make or import a key. A passphrase encrypts it; there is no way to skip that, because this key can end every grant it ever issues.
2. Fund it. The console shows the address and waits. Send it testnet KAS from a testnet-10 faucet — a grant is funded out of that coin, so nothing can be issued until something arrives.
3. Issue a grant. A budget, the most it may spend at once, and who it may pay. One click adds the demo API, which is a real endpoint that sells something.
4. Take the agent key. Shown once. Move it to wherever the agent runs. Without it the grant can still be revoked, but never spent.
5. Watch, and end it. A grant's address moves every time it pays someone; the console follows it. Revoking returns what is left.

What it asks for, which is almost nothing

• Two permissions. storage, to hold your encrypted key and your grant records. alarms, to lock itself when you walk away.
• No host permissions, and no content script. It cannot read a page you visit, because it never runs on one.
• No remote code. Nothing is fetched at run time — no scripts, no fonts, no analytics. There is no server.
• One connection out: a WebSocket to the Kaspa node you point it at, carrying four methods. Change the node and that changes with it.
• Testnet only. Mainnet is refused rather than defaulted, and will stay that way until the covenant has had a review it has not yet had.

The whole policy is in PRIVACY.md, and it is short because there is nothing to disclose.