> For the complete documentation index, see [llms.txt](https://ola-foundation.gitbook.io/ola-documentations/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ola-foundation.gitbook.io/ola-documentations/ola-network-core-components-onis-and-massive/onis/3.-ola-solution-a-trust-minimized-btc-cross-chain-network/3.3-trust-nobody-bridge-yourself.md).

# 3.3 Trust Nobody, Bridge Yourself

**Ola** is a decentralized cross-chain bridge infrastructure framework. Anyone can use Ola to build their own cross-chain services. Based on the ZKVM-OlaVM architecture, Ola efficiently generates Zero-Knowledge Proofs (ZKPs) for multi-chain synchronization.

Ola follows the principle of "Trust nobody, bridge yourself." Projects or users can register through Ola Service and create their own cross-chain bridges. This includes appointing trusted Supervisors to monitor state synchronization, deploying Update contracts on the Receiver Chain with one click, and utilizing the powerful Massive consensus network for full-chain state synchronization.**Terminology**:

* **Supervisor**: Monitors the ChainInfo results. If the ChainInfo reported by multiple Supervisors differs from the synchronized results, the receiving chain can adopt different acceptance strategies.
* **Proposer**: A regular synchronizer who initiates transactions by deploying contracts on the Ola chain. The contract verifies permissions and records statistical outcomes.
* **Ola Synchronize Contract**: Records the voting results of Supervisors and Proposers and determines whether the result is accepted based on custom strategies.
* **Ola Verifier Contract**: The contract that performs verification, which can be replaced by other verification layers.
* **Update Contract**: The verification contract on the Receiver Chain that decides whether to accept and update the Sender Chain's state based on custom logic.