> 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/roadmap-development.md). # Roadmap Development #### **Phase 1 — Core Authorization Primitive** **Objective:** Prove that accountless, authorization-based banking is technically viable. Key deliverables: * Liquidity Fog Pool smart contracts * Zero-knowledge authorization proof system * Stateless intent execution engine * Basic spending constraint framework * $KREDO staking for proof verification Focus: * Correctness * Security * Minimal viable authorization flow This phase establishes Kredo’s foundational architecture #### **Phase 2 — Programmable Permissions & Identity Expansion** **Objective:** Expand expressiveness of authorization logic. Key deliverables: * Advanced ZK identity proofs * Role-based and contextual permissions * Time-bound and purpose-bound spending * Delegated and revocable permissions * SDKs for application integration Focus: * Developer adoption * Composability * Privacy-preserving identity abstraction Kredo begins to function as a **permission layer for finance**, not just a payment system. #### **Phase 3 — Ecosystem & Liquidity Scaling** **Objective:** Transform Kredo into shared financial infrastructure. Key deliverables: * Multi-pool liquidity fog architecture * Cross-application permission reuse * Scalable intent batching and aggregation * Expanded validator and verifier network * Governance activation for policy evolution Focus: * Capital efficiency * Network effects * Economic robustness At this stage, Kredo supports complex financial flows without accounts or balances. #### **Phase 4 — Global Financial Access Layer** **Objective:** Position Kredo as a foundational layer for future finance. Key deliverables: * Enterprise-grade authorization frameworks * Regulated access modules (without custody) * AI and autonomous agent spending primitives * Cross-chain or multi-settlement integrations * Formal verification of authorization invariants Focus: * Long-term sustainability * Institutional-grade reliability * Machine-native financial interaction Kredo evolves into an **authorization-native financial operating system**. --- # 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/roadmap-development.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.