Kalyx

Docs

Super Intelligence Validators

A Super Intelligence Validator is a proof-of-stake validator with a quantum-proof key. A model may decide what the next block should contain. It cannot sign that block. The signature is ML-DSA-87. The key that produces it is the thing the model must never see.

This is the standard. It is not a description of a live fleet. The private testnet runs two genesis validators. They are ordinary stake. No model is signing.

Five jobs, kept apart

  1. Stake. Weight on a validator public key. It is what makes that key eligible for a slot. Without it, the beacon will not assign the key a turn.
  2. The validator key. An ML-DSA-87 key. Public key 2,592 bytes, signature 4,627 bytes. This is the key the beacon knows.
  3. The signer. The only place that key is allowed to live. Hardware, a process on another machine, or a two-of-three. It signs a request that matches its rules, and it can say no.
  4. The agent. The model. It reads the chain, builds a proposal, and asks the signer to sign. The ask is not a command. A refusal is a normal answer.
  5. The watch. Alerts when a signer is asked for something odd, when a key is used in a way it should not be, when slots start going empty. A person receives the alert. The model does not get to mute it.

The order that keeps the key out of the model

  1. Create the validator key inside the signer. Not in the agent’s memory, not in a chat, not in a file the agent can open.
  2. Put 40,000 KALYX behind that public key through the deposit in the validator steps. The agent does not hold that deposit.
  3. Point the agent at the local signer, so a duty is a request. The key stays in that program.
  4. Give the agent a narrow door. It may submit a proposal and learn whether the signer accepted it. It may not export the key, read the seed, read the keystore password, or edit the signer’s rules.
  5. Start with one agent, one signer, and one person who can unplug the agent without unplugging the signer.
  6. Rotate the key on a schedule the agent does not choose. Rotation is a human or a signer policy. It is not a prompt.

What the agent is allowed to know

The public chain. The validator’s public key. Whether the last request was signed. The reason, if the signer refused. That is enough to propose.

What the agent is not allowed to know

The seed. The mnemonic. The keystore password. A copy of the signing key. Any share of a two-of-three that would let it reconstruct the key. Logs that happen to contain those things are a bug, not a feature.

Anything a model can read, someone can try to talk it into repeating. A prompt is not a lock. The signer holds the key.

Before this is real on Kalyx

The local signer is the door an agent may ask. It is not switched on for the two genesis validators, and creating a key there does not put that key in the set. To join, follow the node page: your own synced node, one new key, and a deposit of 40,000 KALYX. The two validators running now are ordinary stake. No model is signing them.

What this page is not

It is not a product you can turn on from a dashboard. It is not custody of anyone’s coins. It is not a claim that the model is aligned, or that the chain is finished, or that the clients have been audited. A model may draft the block. The signer decides whether to sign it.