> For the complete documentation index, see [llms.txt](https://docs.flock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flock.io/flock-tokenomics/token-utility/supply.md). # Supply ### 1. Emission FLock's ecosystem will feature `FLOCK` tokens, set to be distributed to various stakeholders through an initial token emission and a strategically designed reward allocation system over time. Participants will receive rewards in FLOCK tokens based on their contributions to the system. The total supply of `FLOCK` is capped at 1 billion tokens. See [here](/flock-tokenomics/token-allocations.md) for token allocations details. ### 2. Slashing FLock has robust mechanisms in place to ensure the system's integrity and reliability by penalising participants who engage in malicious activities. Specifically, in FL Alliance, if a participant is found to be violating the system's rules or attempting to undermine the network through malicious actions, they may face slashing. Parts of the slashed tokens are rewarded to the honest participants (specifically, it goes to the ones who call the slashing function). This slashing mechanism protects the system from immediate threats by removing or deterring malicious actors, thereby fostering a culture of trust and cooperation among participants. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flock.io/flock-tokenomics/token-utility/supply.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.