The GLaDOS utility token
The constraint that shapes everything
A kernel cannot gate itself. The images on this site are public, the machine runs in ring 0 with one address space and no process isolation, and the operator is by construction the most privileged thing on it. A balance check compiled into the kernel is one edit away from deleted, and anyone who wanted it gone would have both the source and the motive.
It would also cost the project the only property that makes it credible, which is that you can download an image, boot it, and watch it do what the documentation says. A system that refused to run without a wallet would be asking to be taken on trust, which is the opposite of what everything else here is arranged to avoid.
So the rule is that the token gates what a machine must be given, never what it does once it has it. Enforcement lives where the bytes come from, and every item below is on the list because it survives that test.
What it would gate
| Use | Why it is enforceable |
|---|---|
| Signed release channel | The kernel already stages updates: a new image and a detached signature are checked against a key before the next boot swaps them in, with a verified rollback copy. You cannot patch your way into an image you were never sent. This is built and driven end to end; what it lacks is a provisioned key, which the project needs regardless. |
| Model weights | The larger checkpoints, and any finetune trained against the machine's own corpus, are files that somebody distributes. Gating distribution is enforceable because it is distribution. |
| Hosted inference | The kernel has DNS, TCP and a TLS 1.3 client it negotiates itself, so a larger remote model that the in-kernel one escalates to is reachable. The key is issued and checked server-side. It is also a real feature: a 0.6B model in a kernel has obvious ceilings. |
| Ledger anchoring | The interesting one, and not a gate at all. See below. |
Anchoring the self-modification ledger
This system already modifies itself. It proposes changes to its own routing, trains an adapter over its own decision layer, and adopts a change only when four independent judges agree. Each verdict goes in a ledger, and because the search walks a declared grid with no random seed anywhere in it, every verdict is re-derivable bit for bit by any later run. Storage is content-addressed, so a snapshot is one root hash.
None of that was built with a chain in mind, and all of it is already the shape of a chain commitment. Anchoring each root and each ledger entry gives something that does not otherwise exist: a public, timestamped, tamper-evident record of an AI system rewriting itself, where a third party can take a root, re-derive the verdict independently, and check whether it holds. The token pays for anchoring, and can fund a challenge bond, so that disagreeing with an anchored verdict and being right is worth something.
That is the honest reading of the phrase "tokenized operating system". Not that the software checks a balance, but that its history of changing itself is a public record somebody other than its author can verify.
What it deliberately would not do
- Gate boot, or any local feature. Unenforceable, for the reasons above, and it would cost the project the thing that makes it worth looking at.
- Let holders override the judges. Governance can steer which proposals get tried. It must not decide which get adopted. The judges are the measurement discipline this whole project rests on, and a vote that could overrule one would be adopting changes nobody measured.
- Put a key-holding wallet in the kernel. One address space, no process isolation, and a language model with function-call access to raw memory and I/O ports. That is the worst available place to keep a private key. Signing stays off the machine.
Where it stands
The ticker is not finalised. The design above is, in the sense that it is what the project would build rather than a list of options, but nothing has been deployed and no date is set. When something exists, its contract address will be published here and on the source repository, and nowhere else.