Roadmap

What exists, and what does not

Two of these are built and three are not. The three are labelled the same way everywhere on the site, read from one file, so they cannot quietly start sounding real.

1. 01

   The console

   done

   Agents, chat, a terminal, a JavaScript sandbox, a page reader and a scheduler, all running on your device against your own provider key.

2. 02

   Reading the chain

   done

   GIWA Sepolia read straight from the page, no proxy and no provider key, because the RPC allows cross-origin reads.

3. 03

   A relay

   done

   Watches keep running with the tab closed. It never asks for your provider key: a relay you upload a key to would make the promise on the rest of this site false, and encrypting it there would not change who can read it at run time. Watches need no key from anyone. Agent tasks on the relay run on the operator's key under a quota, and are refused with a reason when no operator key is configured.

4. 04

   Paying per call on GIWA

   planned

   Running an agent for someone who has no provider key means someone pays for the call. On-chain settlement is the obvious answer and nothing is deployed.

5. 05

   Agents that hold an address

   planned

   An agent with its own key could read and write on GIWA by itself. That is a large amount of trust to hand a language model, so it comes last and behind a lot of limits.