# Create committees

1.Connect your wallet to [BoolScan's Dashboard](https://dashboard.boolscan.com/?network=testnet).

<figure><img src="https://362083554-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBPzEwQWF8yFmEtNtg2pz%2Fuploads%2FB5B5oBi9UItgdxBTnkS9%2F1706701905010.png?alt=media&#x26;token=4b017573-bb2e-418b-b44b-d642a1d0f20b" alt=""><figcaption><p>Create Committees - Connecting wallet</p></figcaption></figure>

2.Click `+` button on the "Committee" section to start creating a committee.

<figure><img src="https://362083554-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBPzEwQWF8yFmEtNtg2pz%2Fuploads%2FM9kkNshUXy1LGCIgQLLp%2F1706702676989.png?alt=media&#x26;token=ac3b0766-0a4b-49ca-a30e-164f127f1fba" alt=""><figcaption><p>Create Committees - Starting creation</p></figcaption></figure>

3\. One can configure the number of MPC nodes (which is labelled as "`Member`") to control a committee. In general, the number of committee members is positively correlated to the security level while it conversely delays the average time for processing cross-chain messages.&#x20;

By clicking on `Submit`, a user is required to send a transaction to create a committee and record the committee information on the Bool chain.&#x20;

<figure><img src="https://362083554-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBPzEwQWF8yFmEtNtg2pz%2Fuploads%2FzuohDmNBtjTJo5xoZmS0%2F1706704802486.png?alt=media&#x26;token=09d74999-98a0-454f-8f3e-76c2b48c5f83" alt=""><figcaption><p>Create Committees - Sending the creation transaction</p></figcaption></figure>

{% hint style="warning" %}
NOTE that the current Bool testnet only supports a small size of committee members, such as 3 or 5. A higher configuration of the committee members may raise the warning of <mark style="color:red;">`Insufficient devices`</mark>!
{% endhint %}

4\. When the preceding transaction has been submitted, a user should be able to view his newly created committee in his Dashboard.

Primary information for a committee has been provided once the creation transaction is completed.   The name of each committee is initially given as `default` while the committee creator can change the name to a meaningful one, such as "the prospective bridge/application name" + "the blockchain id". &#x20;

<figure><img src="https://362083554-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBPzEwQWF8yFmEtNtg2pz%2Fuploads%2FFp2mKul7Rvknslk19q1q%2F1706703320890.png?alt=media&#x26;token=5be1b53f-1608-47e5-b088-6605ba4cd769" alt=""><figcaption><p>Create Committees - Primary information</p></figcaption></figure>

5\. **Configurations!** You have mastered how to create an ECDSA-type committee in Bool Network. However, please note that a committee can only be used once in Bool Network which means that **at least two committees** are required to be created before building a bridge.&#x20;

* Just created one committee? Why not go above and try the creation process again?
* Have owned more than two committees? Forward to the next page and build an AMT bridge!

{% hint style="info" %}
Remind that each committee manages a private key in Bool Network. At the creation stage of a committee, a unique private key will be assigned to it and instantly distributed into fragments that are stored in the TEE hardware of its MPC-based members. The number of fragments equals the number of committee members.&#x20;
{% endhint %}