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

<figure><img src="https://2970403064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwOUbJmiTegGBEv1M988A%2Fuploads%2FgEQFHe4FnnAM14z6LIfU%2FEcosystem%20Deployment%20Map.png?alt=media&amp;token=7413aae4-eb71-42ae-8495-2a66caf378d7" alt=""><figcaption></figcaption></figure>

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