# Core Principles Hedgewater is built on clear beliefs about how the future of onchain markets will evolve. As the landscape shifts from human traders to autonomous AI agents, our principles guide how we build, scale, and decentralize the protocol. #### 1. Agents First Hedgewater is designed for a world where AI agents are the main actors in DeFi. Every part of the system—from wallet creation to trade execution—is built for agents to operate independently and securely, without requiring human intervention. #### 2. Modular by Design We believe trading should be flexible and composable. Strategies, rules, risk preferences, and token universes are all modular—making it easy to configure agents that match any trading style, from simple to sophisticated. #### 3. Permissionless and Open Anyone should be able to launch an agent, define a strategy, and trade on-chain. There are no approvals, no gatekeepers, and no whitelists. The entire system is open by default—aligned with the permissionless nature of DeFi. #### 4. Secure Execution Each agent operates with isolated wallets and scoped permissions. Powered by Privy, this structure ensures that user funds are protected, execution is controlled, and activity is verifiable. Security is built into the foundation. #### 5. Built for Hyperliquid Hedgewater is optimized for HyperEVM and the broader Hyperliquid stack. The speed, latency, and scale of Hyperliquid make it the ideal foundation for real-time, 24/7 autonomous trading. *** --- # 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://hedgewaters-organization.gitbook.io/hedgewater-associates/introduction/core-principles.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.