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

# Bridgeless Cross-Chain Integration Modules

Covenant system eliminates all bridges, federations, and third-party authorities for cross-chain BTC movement. Instead, it uses a suite of intrinsic, bridgeless, chain-agnostic integration modules that enable native Bitcoin liquidity to flow into any EVM-compatible ecosystem in a fully deterministic, distributed, verifiable, and censorship-resistant manner.

### Core Design Principles

* Bridgeless – No external validators, multisigs, or off-chain parts or bridges exist among Covenant system and the integrated chain.
* Chain-agnostic – The integrated chain cannot influence Covenant operations systemic state, security, or finality. Covenant system remains robust and inherits only Bitcoin-grade guarantees.
* Fully on-chain & verifiable – Every cross-chain state transition is publicly auditable using only finalized state already committed on Covenant system and integrated on-chain networks.

### Architecture of a Cross-Chain Integration Module

Bitcoin and each supported EVM chain (Hyperliquid, Ethereum, Arbitrum, Base, etc.) has its own dedicated integration module composed of two components:

1. Cross-Chain Connector Module\
   A deterministic Covenant programmable module that:

   * Maintains an exact, canonical state of the integrated chain’s finalized block tree inside Covenant based on integrated network' finalized data
   * For its state replica management applies the identical rules used by the target chain itself
   * Manages provision of verified state roots and transaction inclusion proofs to Covenant system modules and handles processing of cross-chain messages above networks

   Because finality is determined using the integrated chain’s own native rules, the connector is completely agnostic and immune to reorgs or manipulation attempts originating from the integrated chain.
2. Dedicated Collator Set\
   A permissionless public distributed set of rotational collator master nodes are programmed to:
   * Deterministically fetch, verify and submit finalized headers from the integrated chain 
   * Verify already finalized cross-chain messages as an additional security layer
   * Are obliged to receive and process incoming block state data from any interesting party
   * Are economically incentivized with system fees and slashable via smart contract managed reward/punishment policies of Covenant system

Collators have no custody, no authority to project any of sole power and no ability to block user exits. All collator activities are public and transparent.

Because collators only operate with already-finalized data and cannot mint, freeze, or steal assets, the integration remains trustless and bridgeless by design.

Covenant’s cross-chain integration modules therefore represent the production-grade mechanism that delivers true wrapless Bitcoin liquidity to any EVM ecosystem while preserving Bitcoin-native security and self-custody guarantees end-to-end.

### Security & Trust Model

| Risk                          | Traditional Bridges | Covenant Integration Modules               |
| ----------------------------- | ------------------- | ------------------------------------------ |
| Third-party custody           | Yes                 | No                                         |
| Validator collusion           | Possible            | Impossible (no signing power)              |
| Integrated chain reorg attack | Possible            | Impossible (follows native finality rules) |
| Censorship of exits           | Possible            | Impossible (any collator can advance)      |
| Single point of failure       | Yes                 | No                                         |

Covenant doesn't use any bridges or other third parties for BTC cross-chain transfer mechanics. Instead, Covenant uses its intrinsic chain-agnostic integration modules for cross-chain integrations. All cross-chain activities are distributed, open, on-chain verifiable, and censorship-resistant.

Covenant utilizes bridgeless chain-agnostic cross-chain integration modules to handle cross-chain activities.

* Bridgeless: connections don’t require 3rd party bridges.
* Chain-agnostic: Covenant integration is designed to exclude any influence from integrated chains.

Each cross-chain integration is based on:

*  a dedicated Covenant cross-chain connector module reflecting rules and specifics of a certain chain;
* a dedicated Collator master nodes that maintain this integration' processes validation.

Cross-chain connector module is an intrinsic Covenant module responsible for Covenant<>Integrated network cross-chain operations handling and validation. This module is responsible for maintaining the integrated network’ block tree state within Covenant and maintaining cross-chain transactions.&#x20;

{% hint style="info" %}
Each cross-chain connector module performs integrated network' block tree state management in accordance with the same rules the integrated network itself does.&#x20;
{% endhint %}

Connector smart contracts consider integrated network' block finalized by the same logic it is considered finalized on the integrated network itself. These mechanics make Covenant closs-chain integrations chain-agnostic and resistant to attempts to manipulate incoming cross-chain transactions.