# Quality of Service

Stake-weighted quality of service (QoS) refers to the allocation of network resources, such as block space and transaction processing capacity, based on the amount of stake committed by validators or stakers. Under this model, a validator with 1% stake would have the right to transmit up to 1% of the packets to the epoch leader and would be capable of resisting Sybil attacks from the rest of the network. Commercial RPC infrastructure operators and entities hosting their own validator nodes and RPC nodes would benefit the most from this, as RPC nodes could include more transactions in blocks by agreeing to peer with validators, and validators may sell more capacity to RPC nodes. 

### How does swQoS work?

For example, if there are two validators—one holding 2% of the stake and the other holding 0.2%—the former will be able to submit up to 2% of the packets to the block producer, taking priority over the latter. This provides the higher-quality validator with better performance and increased Sybil resistance.

<figure><img src="https://2113331469-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzYM0pEemeu6F3UKGPAZE%2Fuploads%2FxRADjBj4yovu5Avwkmyt%2Fimage.png?alt=media&#x26;token=423ad627-3172-4142-93a6-f415ae2a2bd6" alt=""><figcaption></figcaption></figure>

In simple terms, each transaction comes with weight. The heavier it is, the more likely your transactions get through. Consequently, the more you have at stake, the higher the quality of service you will receive, and the less likely it is that malicious flooding from lower-quality validators will affect you.


---

# 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://solayer-labs.gitbook.io/solayer-docs/solayer-overview/endogenous-avs/quality-of-service.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.