> 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/core-infrastructure/full-stack-defi-infrastructure.md).
# Full-Stack DeFi Infrastructure
zkCross is full-stack DeFi infrastructure in the literal sense. It covers the full lifecycle of capital movement rather than only one layer of the stack.
Most systems in this category own one component and rent the rest. They may rely on external bridges, outsourced routing, vendor-managed signing, or loosely coupled monitoring. That can work in simple conditions, but it limits control and introduces trust assumptions.
zkCross approaches the problem differently.
It combines multiple layers into one integrated execution stack:
### Cross-chain routing
zkCross routes value across supported chains and venues inside defined policy boundaries. Routing is not left to discretionary off-chain logic. It is constrained by allowlists, risk limits and settlement requirements.
### Deterministic control
Every proposed action is evaluated against explicit rules before execution. This includes protocol allowlists, asset restrictions, exposure caps, slippage limits, oracle checks, rate limits, cooldowns and circuit breakers.
### Secure signing
zkCross supports permissioned signing architectures appropriate to the environment, including MPC-based signing where relevant and decentralised signing paths in non-EVM environments such as ICP.
### Settlement verification
Execution is not assumed correct simply because a transaction was submitted. zkCross verifies receipts, balance deltas, position outcomes and accounting consistency against expected bounds.
### Monitoring and reconciliation
The system continuously monitors venue health, execution drift, oracle behaviour and state reconciliation. This allows the stack to detect anomalies early and contain risk when needed.
Because these components sit inside one execution framework, zkCross can offer something most systems cannot: end-to-end control over what is allowed, what is signed, what is executed and what is accepted as valid after settlement.
---
# 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/core-infrastructure/full-stack-defi-infrastructure.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.