# Overview The purpose of Saga Security Chain (SSC) is to enable validators to join in providing security to other chains that are launched on the Saga platform. This is made possible by delegators staking their tokens with validators on SSC, thereby strengthening the SSC network. The Saga Security Chain is based on CometBFT, which relies on a set of validators responsible for committing new blocks in the blockchain. These validators participate in the consensus protocol by broadcasting votes with cryptographic signatures signed by each validator's private key. Validator candidates can bond their own tokens and have them "delegated" or staked to them by token holders. At the onset, the Saga Security Chain will launch with 20 validators. The selection of these validators is based on who has the most tokens delegated to them—the top 20 validator candidates with the most voting power become the active validators of the Saga Security Chain. Validators and their delegators earn tokens as block provisions and transaction fees through the execution of the Tendermint consensus protocol. It's worth noting that validators have the option to set a commission on the fees their delegators receive as an additional incentive. If validators engage in misconduct, such as double-signing or being offline for a prolonged period, their staked tokens (including those of users who delegated to them) can be at risk of being slashed, with the penalty varying based on the severity of the violation. For a detailed overview of the Saga Security model, please see [Saga Shared Security](https://docs.saga.xyz/introduction/saga-overview/saga-shared-security). --- # 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://nodedocs.saga.xyz/introduction/overview.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.