> For the complete documentation index, see [llms.txt](https://kredopay.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kredopay.gitbook.io/documentation/technology-overview.md). # Technology Overview Kredo is built on a combination of cryptographic primitives and minimalist on-chain design. **Zero-Knowledge Identity & Authorization** At the core of Kredo is zero-knowledge proof technology, enabling users to prove: * Eligibility * Authorization scope * Constraint compliance Without revealing: * Personal identity * Transaction history * Spending patterns * Account-like identifiers These proofs are generated client-side and verified on-chain, ensuring privacy while maintaining strong correctness guarantees. **Liquidity Fog Pools** Liquidity Fog Pools are shared pools of capital where: * Funds are not attributed to individuals * Ownership is intentionally abstracted * Spending is mediated entirely through authorization From the system’s perspective, liquidity exists independently of users. From the user’s perspective, liquidity is accessible only through valid permissions. This design: * Eliminates balance tracking * Prevents wallet-based attacks * Improves capital utilization * Simplifies on-chain accounting --- # 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://kredopay.gitbook.io/documentation/technology-overview.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.