Aperture Institute GLaDOS: an operating system in Rust, with a language model in the kernel
GLaDOS / Token / Link a wallet

Link a wallet

Prove you hold GLADOS and receive a device code for the experimental update channel. The signature costs no gas, moves nothing, and approves no transaction — it is a message, not a transfer.

You need at least 1,000,000 GLADOS. The balance is read server-side from the contract on Robinhood Chain, and read again at every download rather than remembered.

Nothing on this page will ever ask for a seed phrase or a private key. If any page claiming to be this one does, it is not this one. Close it.

1. Choose a wallet

Looking for wallets…

2. Sign

Choose a wallet first.

3. Your code

Nothing yet.

What this does, exactly

Four steps, and the third is the only one your wallet is involved in.

  1. The server issues a single-use nonce for your address and builds an EIP-4361 message naming this domain, the chain and an expiry.
  2. You read that message. It is shown in full below before you are asked to sign anything.
  3. Your wallet signs it with personal_sign, which is prefixed so that a signed message can never also be a valid transaction.
  4. The server recovers the address from the signature, spends the nonce, reads your balance from the token contract, and issues a device code.

The signature proves one thing: that whoever produced it holds the key for the recovered address. It says nothing about a chain or a balance, which is why your wallet does not need Robinhood Chain added to link. The address comes from the signature; the balance comes from a separate call the server makes.

Both addresses are shown below when you sign — the one your wallet reports and the one the server recovered. They must match. If they ever differ, the recovery is wrong and you should not trust the result; that comparison is the check on the server's cryptography, performed by your wallet.

Then, in the kernel

update link <code>
update channel experimental
update check

The code is a bearer token. Anyone holding it can reach the channel, so it is shown once and stored only as a hash — the server cannot read it back to you, and a database leak is not a leak of working credentials. If you lose it, link again; a wallet may hold five at a time.

And what the code buys is narrow, deliberately: the server answers with a build. The build is signed by the same key as the stable channel and installs on any machine. There is no per-machine binding, and the token page explains why there could not be one.