Page cover
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Why SurfLiquid Exists on zkCross

SurfLiquid is not separate from zkCross Network. It is a consumer deployment of the zkCross execution stack.

That distinction matters because it explains why Surf can make strong claims around custody, deterministic control, cross-chain execution and safety.

Surf uses:

  • zkCross vault custody

  • zkCross Guardian enforcement

  • zkCross routing and chain abstraction

  • zkCross signing architecture

  • zkCross settlement verification and reconciliation

This means Surf does not depend on outsourced control surfaces for core execution. It inherits infrastructure that was already built and tested before the consumer product layer existed.

For zkCross, Surf is important as a proof of infrastructure productisation. For readers of the zkCross docs, Surf should be positioned as the first visible product expression of the rails, not as the entirety of the company.


Last updated

Was this helpful?