> 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/cross-chain-integration-governance.md).

# Cross-chain integration governance

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

To validate cross-chain transactions Covenant utilizes DKG FROST sMPC threshold signature groups of Collators nodes.&#x20;

Each cross-chain integration has its own Collator validation system, responsible for certain integration, independent from Consensus and other integrations validation processes (e.g. Covenant↔Bitcoin integration has its own cross-chain validation process, Covenant↔Hyperliquid has another independent validation process, and Covenant has its own Consensus validation, so three different validation processes run in parallel).

Collator groups rotate with shares regeneration, sweep transactions, and with epoch overlap, have witness groups that run in parallel, have reputation, stake and performance criteria, Collator node reputation and stake are slashed for node' proven misbehaviour.
