> For the complete documentation index, see [llms.txt](https://docs.zerodao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerodao.com/development/glossary.md).

# Glossary

### sZERO

sZERO is a non-transferrable ERC20 and represents a balance of staked ZERO, which is read from ZERO network nodes to determine voting weight, should the sZERO holder decide to run a validator.

### Signers

Entities responsible for signing messages using the [FROST](#frost) protocol. 

### Validators

Entities responsible for producing blocks.

### Voters

Entities holding a balance of staked ZERO (sZERO) on Ethereum mainnet, the on-chain governance token.

### Keepers

Entities responsible for relaying transactions onto any supported network, receiving passive revenue based on transaction volume, in excess of fees paid.

### Schnorr Signature

A type of digital signature scheme that allows for the efficient and secure signing of transactions and messages.

### FROST

Flexible Round-Optimized Schnorr Threshold (FROST) is a somewhat natural conversion from secret sharing of private keys to secret sharing of signatures, that is, a protocol describing how to use key shards to construct signature shards which can be put together to construct full signatures without revealing the shared sharded key.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zerodao.com/development/glossary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.