> For the complete documentation index, see [llms.txt](https://token-strategy.gitbook.io/eth-strategy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://token-strategy.gitbook.io/eth-strategy/readme.md). # Welcome to ETH Strategy EtherStrategy (ETHSR) is a tokenized vehicle for ETH accumulation, giving ETHSR holders control of a growing pool of ETH managed through fully transparent, onchain strategies managed by the DAO. EtherStrategy is **entirely onchain and transparent** and built to replicate the success of existing LST protocols while adding unique value accrual mechanisms for accruing more ETH. **Statement from Token Strategy Labs, Inc.** Token Strategy Labs, Inc. reminds participants to exercise caution and only interact with the smart contract within their personal risk tolerance. Blockchain-based systems, including this one, carry inherent risks, and all interactions should be approached with a clear understanding of those risks. There should be no expectation that ETHSR will trade at or above NAV, and it may trade below NAV. Additionally, trading for ETHSR tokens will not be enabled immediately. Smart contracts can have vulnerabilities, and participation should be based on an informed assessment rather than urgency or speculation. Participation from US persons is NOT ALLOWED. --- # 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://token-strategy.gitbook.io/eth-strategy/readme.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.