# Multi-owner dapp deployment and updates · Chromia Docs (concept)

> This guide provides step-by-step instructions for deploying and updating decentralized applications (dapps) on Chromia using multiple private keys and voter…

Source: https://docs.chromia.com/build/deployment/mainnet/multi-deployment/

# Multi-owner dapp deployment and updates

On this page

* [Prerequisites](#prerequisites)
* [Steps for multi-owner deployment](#steps-for-multi-owner-deployment)
* [Steps for updating a dapp](#steps-for-updating-a-dapp)
* [Steps for managing proposals](#steps-for-managing-proposals)
* [Example configurations](#example-configurations)

This guide provides step-by-step instructions for deploying and updating decentralized applications (dapps) on Chromia
using multiple private keys and voter sets. Multi-owner configurations enhance decentralization by requiring consensus
among dapp providers.

### Prerequisites

* A deployed dapp container on Chromia
* Access to Chromia CLI tools (e.g., `pmc`, `chr`)
* Public keys for all intended dapp providers

### Steps for multi-owner deployment

#### 1. Create a container lease

* Navigate to the [Chromia Vault Container lease page](https://vault.chromia.com/en/containers/) to create a container lease.
* Use the specifications required for your dapp.

#### 2. Configure voter sets

* Promote others to dapp providers:

  Terminal

  ```
  chr deployment voterset add-dapp-provider
  ```
* To include additional providers in the voter set:

  Terminal

  ```
  chr deployment voterset list
  ```

  Terminal

  ```
  chr deployment voterset update -vs <voter set name> --add-members <pk1>,<pk2>
  ```

#### 3. Set the voting threshold

Adjust the number of approvals required for proposals to pass:

Terminal

```
chr deployment voterset update -vs <voter set name> --threshold <int>
```

The threshold is calculated as a fraction of total members. For example, setting the threshold to `2` in a set of 3
members requires two-thirds approval.

### Steps for updating a dapp

1. Initiate an update:

   Terminal

   ```
   pmc blockchain update
   ```
2. For multi-owner dapps, ensure all required votes are collected:

   Terminal

   ```
   pmc proposal vote --accept --id <proposal ID>
   ```

### Steps for managing proposals

* List pending proposals:

  Terminal

  ```
  chr deployment proposal list
  ```
* Vote on a proposal:

  Terminal

  ```
  chr deployment proposal vote --id <proposal ID> --accept
  ```
* Withdraw an incorrect proposal (must be done by the creator):

  Terminal

  ```
  chr deployment proposal revoke --id <proposal ID>
  ```

### Example configurations

#### Single-provider configuration

Plain text

```
$ pmc voterset info --name chain_of_alliance
╭─────────────┬────────────────────────────────────────────────────────────────────╮
│ Voter set   │ chain_of_alliance                                                  │
├─────────────┼────────────────────────────────────────────────────────────────────┤
│ Threshold   │ 1                                                                  │
├─────────────┼────────────────────────────────────────────────────────────────────┤
│ Member 0    │ 02FEA5C0D8396B38C50200F2A583DCC8ED23416B9F9700A4AA435D57865939A536 │
╰─────────────┴────────────────────────────────────────────────────────────────────╯
```

#### Multi-provider configuration

Plain text

```
$ pmc voterset info --name chain_of_alliance
╭─────────────┬────────────────────────────────────────────────────────────────────╮
│ Voter set   │ chain_of_alliance                                                  │
├─────────────┼────────────────────────────────────────────────────────────────────┤
│ Threshold   │ 2                                                                  │
├─────────────┼────────────────────────────────────────────────────────────────────┤
│ Member 0    │ 02FEA5C0D8396B38C50200F2A583DCC8ED23416B9F9700A4AA435D57865939A536 │
│ Member 1    │ 0250648F440B481A2E9AD30FD7A34EDFCF698F9D2C4ADD33B3B4836B114CCBEF9E │
╰─────────────┴────────────────────────────────────────────────────────────────────╯

$ pmc container info --name coa
╭──────────────┬────────────────────────────────────────────────────────────────────────────────╮
│ Deployer:    │ chain_of_alliance                                                              │
├──────────────┼────────────────────────────────────────────────────────────────────────────────┤
│ Threshold:   │ 2                                                                              │
╰──────────────┴────────────────────────────────────────────────────────────────────────────────╯
```

In this setup, both providers must approve updates to the dapp.

[View this page on docs.chromia.com](https://docs.chromia.com/build/deployment/mainnet/multi-deployment/)Content mirrored from the live docs
