# 0KN  Servers

### Staked 0KN Servers

0KN Servers are ultimately the fundamental blocks that make up the entire network. They play a crucial role in maintaining the security and integrity of both the proof-of-stake blockchain and the anonymous broadcast mixnet, creating a symbiotic relationship between the two functions. By fulfilling their responsibilities, the staked servers contribute to a decentralized, secure, and robust ecosystem that supports both blockchain transactions and anonymous communication services.

0KN Servers can become active on the network when their owner time-locks a specified fixed amount of $0KN tokens via a registration transaction on-chain. Under the current system design staked servers will receive a base 70% of block rewards with additional rewards belonging to different categories of average bandwidth they provide to the network. 

### Bandwidth

Bandwidth plays an important role in the efficiency and latency improvements of the network. A monitoring mechanism will exist to measure the average bandwidth staked servers provide to the network. They can earn extra block rewards on top the base 70% rate if they belong to more superior bandwidth categories.

### Delegated Staking

Token holders who do not want to run their own staked servers due to hardware requirements or do not have the specified fixed amount to do so can delegate their tokens with other token holders to run staked servers on the network and earn staking rewards in groups of 4. This will enhance decentralization and scaling in the network.

### Slashing

The blame and elimination protocol enables honest servers in the network to assign blame on servers acting maliciously and deviating from the protocol. Once a server is blamed for malicious behavior and eliminated from the network their stake will be entirely slashed and tokens will be burned. 

<figure><img src="/files/9ID3sVn0z6kqinu9E58y" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://000z.gitbook.io/0/network-incentives/0kn-servers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.