> For the complete documentation index, see [llms.txt](https://docs.tranchess.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tranchess.com/product-retirement-tracker/timeline-and-milestones.md). # Timeline & Milestones We will list the steps to discontinue qETH and eQUEEN funds here. The checked ones are the ones that have been completed. *** ### qETH Fund * [x] Close the creation function for qETH. * [x] Remove the qETH-ETH Balancer pool CHESS emission voting option from the governance page. * [x] Close all existing validator nodes. This will take about 5\~10 days to complete. * [x] Upgrade the current smart contract for instant withdrawal support once all ETHs in the validator nodes are redeemed. The upgrade will take 1\~2 weeks. * [ ] We will keep the qETH redemption page up for approximately 3\~4 months, with the exact duration depending on the progress of ETH redemptions. **(In progress)** *** ### eQUEEN Fund * [x] Remove the redemption fee. * [x] Remove the merge fee. * [x] Remove the CHESS emission voting option for “ETH on BNB Chain” from the governance page. * [x] A three-month window: for eBISHOP and eROOK holders to swap back to QUEEN and redeem. During this window, any and all rebalances will be processed as usual. **(In progress)** * [ ] After the 3-month window, change the interest rate to 0 and the t-wap oracle to a constant. This will stop the fair values of eBISHOP and eROOK from changing, preventing future rebalances. * [ ] Close the creation function for eQUEEN. * [ ] Remove the CHESS emission voting option for the eBISHOP-USDC pool from the governance page. * [ ] We will to keep the eQUEEN redemption page up for approximately 3\~4 months. The exact duration depends on the progress of ETH redemptions. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.tranchess.com/product-retirement-tracker/timeline-and-milestones.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.