> For the complete documentation index, see [llms.txt](https://zkcross-network-1.gitbook.io/learn.zkcross.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zkcross-network-1.gitbook.io/learn.zkcross.network/welcome/why-now.md). # Why Now The timing for zkCross is structural, not narrative-driven. Web3 is moving into a phase where infrastructure quality matters more than surface-level novelty. Stablecoin adoption is accelerating. Multi-chain usage is normal. More ecosystems want native DeFi functionality. More applications want embedded yield, routing and cross-chain execution. AI systems are also becoming capable enough to coordinate complex actions, but that capability only becomes useful when it is paired with hard control. That is where zkCross fits. The market no longer needs more isolated apps that depend on third-party execution vendors. It needs infrastructure that can make capital movement programmable, secure and verifiable across heterogeneous environments. zkCross was built before the current AI wave and before DeFAI became a category. The core thesis has been consistent from the start: automation only works at scale when execution remains bounded by design. --- # 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://zkcross-network-1.gitbook.io/learn.zkcross.network/welcome/why-now.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.