Execution Architecture

zkCross Network is an execution infrastructure layer designed to move value across chains safely, with deterministic control over what can happen at every step.

The architecture is built around one key principle: planning and execution must be separated.

A planner, strategy engine, or AI system can propose actions. That does not give it authority. Authority comes only from the execution system, which validates actions against rules, signing constraints and post-settlement checks.

The execution lifecycle

zkCross follows a structured execution lifecycle:

1

Observe

The system reads balances, positions, venue state, price references and network conditions.

2

Purpose

An action is represented as an intent with defined parameters, allowed destinations, bounds and expiry.

3

Validate

The intent is checked against deterministic rules, policy boundaries, simulation expectations and permission constraints.

4

Execute

If valid, the router builds the execution bundle, adapters normalise the action for the target chain or venue and the signing path authorises only the scoped action.

5

Verify

After execution, zkCross collects receipts, compares expected and actual outcomes, reconciles accounting and re-evaluates invariants.

6

Record and monitor

The run is logged in a structured trail that includes observations, intent, checks, transactions, receipts and post-execution verification. Monitoring continues after settlement.

Vault and custody model

Funds remain inside user-owned vault contracts, which form the custody boundary and the execution endpoint.

This matters because zkCross is designed to be non-custodial at the infrastructure layer. The vault is the only approved origin and receiver of value movement. Execution can move funds through approved paths, but it cannot create arbitrary external transfer behaviour outside the defined model.

Core custody properties include:

• The vault is the source and destination of authorised value movement
• Actions must match approved action types and approved destination sets
• Slippage and exposure bounds are enforced at execution time
• Execution paths cannot bypass policy enforcement

This model gives zkCross a clean separation between infrastructure control and user asset ownership.

---