> 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/ecosystem-validation/ecosystem-deployments-and-grants.md).
# Ecosystem Deployments and Grants
zkCross was not built in isolation. It matured through ecosystem-level deployments where the infrastructure had to adapt to real constraints and real users.
### Partisia
zkCross worked with Partisia to deliver the first functional DeFi entry point for the ecosystem. This included AMM infrastructure, cross-chain routing and deterministic execution adapted to privacy-preserving, MPC-oriented smart contract architecture.
### Stellar
On Stellar, zkCross delivered cross-chain liquidity routing between EVM environments and Stellar, unified balance abstraction, one-click liquidity movement and fiat on-ramp integration through Stellar Anchors. The work required adapting execution logic across both EVM and Soroban environments.
### Internet Computer
zkCross integrated canister-based monitoring and chain-key cryptography into its execution stack on ICP. This allowed decentralised signing and monitoring while preserving deterministic execution.
### Arbitrum
Arbitrum served as a high-throughput EVM proving ground where zkCross validated unified liquidity routing, gas abstraction and cross-chain settlement under live market conditions.
### Why the grants matter
The grants secured across these ecosystems were not speculative token incentives. They were non-dilutive funding awarded for infrastructure development, interoperability, security validation and ecosystem enablement.
They matter because they represent real external validation of zkCross’s ability to ship.
---
# 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/ecosystem-validation/ecosystem-deployments-and-grants.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.