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

Monitoring, Reconciliation, and Verification

zkCross treats monitoring as part of security, not just operations.

Every execution run creates a structured trail that can be reviewed later. This includes:

  • observations and state inputs

  • the proposed intent

  • validation results

  • the execution path used

  • transactions and receipts

  • post-execution checks

  • reconciliation outcomes

After execution, zkCross verifies that resulting balances, position changes and accounting states remain inside expected bounds.

Monitoring continues after settlement. The system tracks venue health, oracle drift, liquidity changes, anomaly signals and risk triggers over time.

This is what makes zkCross operationally reviewable and suitable for systems where capital cannot be treated casually.

Last updated

Was this helpful?