# Revenue Share We will soon be introducing a revenue-sharing model aimed at rewarding our stakeholders. Soon, you will have the option to 'lock stake' your tokens via the DAPP, securing a fluctuating percentage share of profits generated through a new rollbit account. Rewards will be distributed in ETH, with a 20% administrative fee. Upon staking, a 1% fee will be applied, accompanied by a weekly 1% reduction in token amount. **Rest assured, these deducted tokens will be permanently removed from circulation, thereby enhancing the value of remaining tokens over time.** Here's the exciting part: despite the reduction in token amount, staking remains advantageous due to potential returns. For instance, staking 1E worth of tokens could yield approximately 1.5 times your initial capital in ETH if we achieve an average x3 return on investment in the first week, even with a 50% win rate (historically, we've achieved over 80% wins.) Each user's earnings are directly proportional to their staked Ethereum. For instance, staking 2 ETH allows the bot to automatically allocate 0.2 ETH for betting purposes. This process is entirely automated—requiring no action from the user—as the bot meticulously manages the betting activities. If the win ratio exceeds 51%, users receive free ETH on a weekly basis as a part of their profit share. We are committed to transparency in profit distribution, allocating 40% to revenue sharing, 20% to buyback/liquidity pool, 20% to development, and 20% to compounding. This framework ensures a mutually beneficial arrangement for all stakeholders. --- # 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://0xbet-1.gitbook.io/0xbet/0xbet-token/revenue-share.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.