# Dynamic Hidden Committee (DHC)

Different from existing cross-chain solutions, Bool Network applies an external verification model to securely process cross-chain messages in a decentralized and distributed manner. Dynamic Hidden Committee (DHC) is proposed to guarantee the security of omnichain applications built on top of it. Each DHC manages a private key in Bool Network and the private key is distributed into key shares and stored in the DHC members, i.e a group of MPC nodes.&#x20;

DHC follows a decentralized signature scheme which uses its underlying private key to sign cross-chain messages and yield signatures as on-chain verifiable "claims" to indicate the validity of cross-chain messages.&#x20;

More specifically, each user in Bool Network can deploy his application-specific DHCs to serve his own application's cross-chain bridge. Bool Network has provided a comprehensive [interface](https://boolscan.com/dashboard/) for its users, i.e. bridge builders, to construct their personal and customizable bridge safeguards (DHC) and on-chain message endpoints ([`Anchor`](https://docs.bool.network/evm-ecosystem/smart-contracts/on-chain-endpoint-anchor/anchor.sol)). &#x20;

{% hint style="info" %}
Bool Network Testnet has been launched and developers can follow the guides provided [here](https://docs.bool.network/evm-ecosystem/amt-bridges) to build bridges and test their cross-chain applications in EVM ecosystems.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bool.network/interoperability-protocol/dynamic-hidden-committee-dhc.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
