> For the complete documentation index, see [llms.txt](https://docs.tradealgoavs.sphenelabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradealgoavs.sphenelabs.com/key-functionalities.md). # Key Functionalities The key functionalities of TradeAlgoAVS includes: 1. Decentralized & Non-Custodial Trading Strategies * Users retain full control over their assets. * Strategy providers monetize their algorithms without revealing their proprietary code. * Execution is performed by off-chain Operators, including AI agents hosted on Autonome. 2. Trust-Minimized Execution & On-Chain Verification * Operators stake funds and are slashed for malicious behavior. * Trading execution is validated using M-of-N statistical aggregation. * Fraud-proof mechanisms detect deviations from expected performance benchmarks. * The goal is to implement WYSIWYG literally what you see when you click subscribe in terms of strategy expected performance statistics should be what you get consistently in the long run. 3. Self-Curating Autonomous Strategies * Strategies are on-chain verified based on real-time performance statistics. * Poor-performing strategies are naturally filtered out. * Strategy providers must backtest and paper trade before publishing. --- # 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.tradealgoavs.sphenelabs.com/key-functionalities.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.