# Burn Mechanism OpenSource implements automatic token burns funded by platform revenue and contributor rewards reserve, creating deflationary pressure through platform activity. ### How It Works **Burn Events** * **1,000 $OS** burned per repository creation * **500 $OS** burned per code commit * Burns funded from platform revenue and contributor rewards reserve * Permanent removal from circulation ### Funding Sources **Revenue-Based Burns** * Platform fees converted to $OS for burns * Infrastructure service payments allocated to burn pool * Premium feature subscriptions contribute to burns **Reserve Allocation** * Portion of contributor rewards reserve designated for burns * Ensures sustainability without impacting user tokens * Transparent on-chain tracking ### Economic Model Platform activity drives token burns. Higher usage creates more burns, reducing supply while revenue streams ensure sustainable funding. The mechanism scales naturally with ecosystem growth. --- # 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.os.codes/overview/tokenomics/burn-mechanism.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.