# Design Principles #### **1. Non-Custodial by Default** Tychi never holds or moves user assets without explicit user-signed authorization.\ Private keys remain local to the device. #### **2. Abstracted Complexity** Gas fragmentation, routing, multi-chain differences, and DApp interactions are abstracted behind predictable flows.\ The system must reduce cognitive load without reducing user control. #### **3. Modular Feature System** All advanced capabilities (gas abstraction, cold wallet mode, debit card, AI modules) operate as independent modules, so the wallet remains lightweight and maintainable. #### **4. Assistive Intelligence, Not Automation** AI modules (like PTI or fee insights) provide guidance and risk signals, but **never** execute, alter, or block user transactions. #### **5. Cross-Chain Uniformity** Regardless of chain (EVM, Solana, Sui, Tron), transaction review, signing, and confirmation follow a consistent interface to avoid user confusion and reduce error rates. These principles define how Tychi behaves across the app, backend systems, chain integrations, and future modules. --- # 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://tychi.gitbook.io/tychi-whitepaper/core-principles/design-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.