> For the complete documentation index, see [llms.txt](https://docs.sire.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sire.bot/products/staking.md). # Staking Learn how staking works and its benefits #### **Overview** Staking connects holders directly to SIRE’s network activity. By staking SIRE, users help stabilise the ecosystem and participate in a fee-based incentive structure that rewards long-term alignment. Stakers receive protocol benefits including reduced αVault fees, access to the token-gated αLink LLM, and eligibility for ecosystem-based rewards as new integrations come online. #### **Mechanics** When you stake SIRE, your tokens are locked in a non-custodial contract that tracks your tier level and unlocks protocol benefits in real time. **Staking Benefits:** * **Reduced αVault Fees:** Lower both performance and withdrawal fees, scaled by the amount of SIRE staked. * **Staking Rewards:** A portion of protocol fees from αVault and future network products is distributed to stakers. * **αLink access:** Stakers unlock the token-gated terminal with live models and market analysis tools. * **Ecosystem Rewards:** Stakers are eligible to receive additional benefits tied to broader ecosystem participation, including integrations with prediction-market platforms and on-chain initiatives aligned with SIRE’s mission. **Staking Tiers:** * 1K SIRE → 18% performance fee | 1.8% withdrawal fee * 5K SIRE → 16% | 1.6% * 10K SIRE → 14% | 1.4% * 50K SIRE → 12% | 1.2% * 100K SIRE → 10% | 1% All staking and fee adjustments occur automatically on-chain. Stakers maintain full self-custody and can unstake at any time, subject to cooldown periods when applicable. #### **Why It Matters** Staking aligns participants with the long-term success of the protocol. It strengthens the feedback loop between αVault, αLink, and the wider SIRE ecosystem, ensuring contributors benefit from transparency and shared growth. As new integrations launch, staking becomes the access layer linking holders to the expanding network of tools, incentives, and market applications built around SIRE. #### **How It All Connects** SIRE operates as a continuous loop between intelligence, execution, and alignment. αLink surfaces live analytical insight from sports data and prediction markets. αVault turns those insights into autonomous, on-chain strategies that generate measurable performance. Staking completes the cycle: rewarding participation, reducing fees, and feeding value back into the network. Together, these elements create a self-learning & compounding ecosystem where every match, signal, and transaction strengthens SIRE’s intelligence engine and supports its long-term sustainability. --- # 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.sire.bot/products/staking.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.