> For the complete documentation index, see [llms.txt](https://docs.peapods.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peapods.finance/peapods-overview/core-principles.md). # Core Principles ### **Core Principles** **Sustainability**\ Peapods does not rely on emissions or inflationary mechanics. Yield comes exclusively from on-chain economic activity and is recycled back to participants. **Transparency**\ All actions, fee flows, governance decisions, interest rate changes are recorded and visible on-chain. There are no admin keys, upgradable contracts, or hidden privileges. \*\ \*Excluding during live beta phases **Accessibility**\ Anyone can turn any ERC-20 token can be turned into a yield-generating Pod via a no-code interface. There is no need for external approvals, governance votes, or technical integration. **Immutability**\ Core contracts are non-upgradable and cannot be paused or changed once deployed. This ensures long-term consistency and eliminates centralized failure risks. \*\ \*Excluding during live beta phases **Aligned Incentives**\ Peapods separates protocol participants into discrete roles such as traders, liquidity providers, lenders, borrowers, and governance participants. Each roles earns value from the protocol in a different way. --- # 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.peapods.finance/peapods-overview/core-principles.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.