Full-Stack DeFi Infra Behind Surf
Surf is not a frontend that is integrated into someone else’s DeFi stack after the fact.
Surf is built on zkCross Network from day one. It is the same team, the same research lineage, and the same execution mindset, now productised into an AI yield agent that can route, rebalance, and enforce risk controls without depending on third-party operators.
What this enables is simple. Surf can feel “easy” on the surface because the hard work already exists underneath it: chain abstraction, liquidity routing, secure signing, automation primitives, and deterministic guardrails, built and shipped by zkCross across multiple ecosystems.
Surf is the product layer. zkCross is the infrastructure layer
Think of Surf as the AI interface and coordination layer, and zkCross as the engine room that makes controlled execution possible.
zkCross Network provides:
Cross-chain movement and routing primitives
Liquidity orchestration and execution rails
Secure signing architecture and key safety primitives
Automation support for multi-step DeFi actions
Monitoring, safety checks, and rule-enforced execution controls
Surf adds:
A vault-based savings UX that normal users can understand
Strategy intelligence that scores risk-adjusted yield paths
A planning layer that proposes actions
A control layer that enforces “what is allowed”
A product experience that turns complex DeFi into deposit, earn, withdraw
This is why Surf can credibly claim native control over infrastructure, intelligence, and execution. It is not stitching together vendors. It is building on its own stack.
What “full-stack” actually means in practice
Most projects in this category own one layer and rent the rest.
Surf is different because the underlying zkCross stack was built to handle the full lifecycle of capital movement and execution:
1. Chain abstraction and cross-chain execution rails
Users do not want to think in chains, bridges, and gas assets. They want outcomes.
zkCross has spent years building the rails that make cross-chain actions feel like a single flow. That includes routing logic, transaction coordination, and the execution patterns needed to move value across ecosystems while keeping the user experience coherent.
2. Liquidity routing and venue integration maturity
Yield routing is not just “find the highest APY”.
A real system needs venue integrations that can survive production conditions: liquidity fragmentation, changing incentives, sudden utilisation spikes, and adverse execution paths. zkCross has built the operational muscle to integrate, test, and ship DeFi infrastructure across chains, which is what Surf inherits as a baseline.
3. Secure execution primitives and signing safety
When automation touches real money, key management and signing flows stop being “implementation details”. They become the product.
zkCross has built and shipped signing and execution systems designed for secure, repeatable, controlled behaviour at scale. Surf relies on those primitives so the AI layer does not become a single point of failure.
4. Deterministic controls and monitored automation
Surf is not “an AI that moves money”.
Surf is an AI system where decisions are constrained by deterministic controls. The automation layer is designed to propose actions, validate them against hard constraints, and only then execute within bounds. This is the execution standard that separates a consumer product from a risky experiment.
Battle-tested infrastructure across real chains
Over the past three years, zkCross has operated as an infrastructure-as-a-service partner to blockchains, working directly with core teams to solve DeFi-level gaps that could not be addressed by surface integrations alone. This work has involved building chain-native execution layers, cross-chain liquidity rails, secure signing systems, and automation primitives that now form the foundation Surf runs on today.
This infrastructure was not built in isolation. It was designed, deployed, iterated, and hardened inside live ecosystems, under real constraints, with real users and capital at stake. All core components have undergone independent security reviews and audits by Halborn, and the same execution stack is now productised inside Surf.
Partisia Blockchain
On Partisia, zkCross worked as an infrastructure extension of the chain team, delivering the first functional DeFi entry point for the ecosystem.
This included building and launching the first AMM DEX on Partisia, alongside the surrounding cross-chain and execution infrastructure required to make DeFi viable on a privacy-preserving chain. The work involved solving blockchain-level gaps rather than deploying an off-the-shelf protocol, and required deep collaboration with the Partisia engineering team over more than a year.
The result was a production DEX that enabled native swaps, cross-chain liquidity movement, and fiat on-ramp connectivity, positioning zkCrossDEX as foundational infrastructure for Partisia’s DeFi layer.
Stellar
With Stellar, zkCross focused on bridging DeFi infrastructure gaps at the ecosystem level, particularly around liquidity, interoperability, and fiat accessibility.
zkCross designed and delivered Stellar zkCrossDEX as a cross-chain execution and liquidity layer, leveraging Stellar’s native DEX and Anchor ecosystem while abstracting complexity for users. This included one-click cross-chain liquidity movement from EVM chains, direct fiat on-ramps via Anchors, and unified asset routing that removed the need for centralised exchanges as an onboarding step.
The work was structured in phased delivery, covering protocol integration, wallet connectivity, unified balance management, and ecosystem growth tooling. This positioned Stellar to support DeFi use cases with measurable TVL, on-chain volume, and a clearer developer surface for future applications.
Internet Computer (ICP)
On ICP, zkCross has focused on deep infrastructure innovation, particularly around decentralised security and trust minimisation.
zkCross integrated ICP canisters into its execution stack to decentralise cross-chain transaction monitoring and signing. This replaced centralised indexers and key management with canister-based automation and chain-key cryptography, ensuring that private keys are never exposed, even to zkCross itself.
This work laid the foundation for fully decentralised cross-chain execution and enabled the next phase: launching zkCrossDEX on ICP with native liquidity onboarding, fiat access, and secure cross-chain swaps. The integration demonstrates zkCross’s ability to adapt its execution layer to non-EVM architectures while preserving deterministic behaviour and security guarantees.
Arbitrum
Arbitrum serves as a high-throughput execution environment where zkCross deployed and scaled its cross-chain trading and abstraction primitives under real market conditions.
On Arbitrum, zkCrossDEX demonstrated chain abstraction, unified liquidity routing across multiple EVM chains, gas abstraction, and fiat on-ramp integration, enabling users to trade across ecosystems without manual bridging or operational overhead. This environment validated the performance and reliability of zkCross’s execution layer at scale, handling high-frequency interactions and meaningful trading volume.
The learnings from Arbitrum directly informed the automation, routing, and risk enforcement logic that Surf now uses for vault execution and rebalancing.
Independent Security and Audits
zkCross infrastructure has undergone multiple independent security reviews and audits by Halborn, covering both EVM and non-EVM components, as well as penetration testing.
Halborn case study:
https://www.halborn.com/case-studies/post/case-study-ensuring-security-for-zkcross-network-s-defi-infrastructure-with-halborn
Audit reports:
https://www.halborn.com/audits/zkcross/evm-stellar-zkcrossdex-5ec240 https://www.halborn.com/audits/zkcross/soroban-zkcrossdex-72ebe2 https://www.halborn.com/audits/zkcross/zkcross—penetration-test-fe0782
These audits validate the security assumptions behind the execution stack Surf relies on today.
Why this matters for Surf users
Most “AI vault” products are wrappers around third-party protocols, where the project owns the interface but not the execution stack.
Surf is built on an execution foundation that was engineered to handle:
Cross-chain routing and liquidity movement without brittle manual flows
Secure signing and controlled execution designed for deterministic behaviour
Automation that is bound by rules rather than trust in an operator
Production-grade integration maturity across multiple ecosystems
This is the foundation Surf stands on. It is what makes Surf feel simple without being fragile.
Last updated