# Scaling ### Limitations of TSS mission Together with the YAR protocol, the YAR chain controls the main memory - the YAR vault. This consensus can only grow so large, making TSS too slow. As soon as the key generation process takes too long, the main memory is divided by 2. This process is repeated until the network reaches either the "block consensus limit" or the "economic limit" described below. ### Block consensus limit The YAR chain is based on the PoS consensus. The target rate for creating new blocks is 5 seconds or 15Mb. When a block size reaches 15Mb, a block is validated, no matter how much time has passed since a previous block. This is to increase the speed of the blockchain during peak loads. ### Economic limit The blockchain strives to be decentralized, so it does not limit the number of nodes that can participate in block validation. At the same time, the dominant consensus of the network is PoS, so there is a local limit on the number of nodes, which is calculated by the formula: [total circulating coins / staking size = local maximum number of nodes](#user-content-fn-1)[^1] The validator's reward is calculated by the formula: [2YAR (block validation reward) + transaction fee = validator reward](#user-content-fn-1)[^1] The consensus takes into account the need to manage the economy of the network. Therefore, the staking amount, the reward for block validation, and the inclusion/exclusion of transaction fees in the reward to the validator can be reduced/increased by voting by the participants of the YAR DAO. [^1]: --- # 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://docs.yarchain.org/whitepaper/project-mechanics/scaling.md?ask= ``` 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.