> For the complete documentation index, see [llms.txt](https://cvnnt.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cvnnt.gitbook.io/documentation/system-architecture/governance/covenant-verification-model/distributed-verification-structure.md).

# Distributed verification structure

{% hint style="info" %}
Note: This chapter is currently under development.
{% endhint %}

Covenant verification process is open, distributed, onchain and public. Covenant verification architecture consists of several validation processes that exist independently and simultaneously, run in parallel by independent group formations. These validation processes include Covenant data\&state validation and cross-chain integration validations. Each cross-chain integration has its own Collator validation process responsible for certain integration, independent from other validation processes.

Example: Covenant↔Bitcoin integration has its own cross-chain validation process on Covenant, Covenant↔Hyperliquid integration has another independent validation process, and Covenant has its own Consensus validation, so three different validation processes run in parallel.

<figure><img src="https://content.gitbook.com/content/IrCs7se0X60UkwSdNUVw/blobs/9pzg9sjKRQOYD17nWHA9/image.png" alt=""><figcaption><p><em>Covenant system has multiple independent simultaneous validation processes (this scheme demonstrate state verification and two independent cross-chain validations for two integrations (e.g. Covenant↔Bitcoin integration and Covenant↔Hyperliquid integration).</em></p></figcaption></figure>