> 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/what-zkcross-network-solves.md).

# What zkCross Network Solves

DeFi grew quickly, but its infrastructure did not mature at the same pace.

Liquidity is spread across isolated blockchains. Users must bridge manually, manage different wallets, hold different gas assets and navigate different execution environments. Developers face the same problem at the systems level. To build a serious cross-chain product, they often need to integrate multiple vendors for routing, bridging, signing, settlement, monitoring and security.

This creates three persistent problems.

<figure><img src="/files/kzIckflAtDjLPrc6MCyv" alt=""><figcaption></figcaption></figure>

### 1. Fragmented execution

Moving capital across chains still depends too often on brittle third-party paths. Bridges introduce key risk. Routers introduce external dependencies. Settlement can become hard to verify end to end.

### 2. Fragmented liquidity

Capital exists across chains, but accessing it efficiently is difficult. Users face friction. Ecosystems struggle to activate local DeFi depth. Developers waste time abstracting infrastructure instead of building products.

### 3. Automation without enforceable control

AI and automation systems can propose actions, but they do not automatically become safe just because they are intelligent. Without deterministic boundaries, automation scales mistakes faster.

zkCross was built to solve these problems at the infrastructure layer.

It gives capital movement a controlled execution environment where routing, signing, settlement and monitoring all operate inside explicit, enforceable rules.


---

# 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/what-zkcross-network-solves.md?ask=<question>&goal=<endgoal>
```

`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.