Skip to main content

Add a dapp provider to your container voter set

When you lease a container, you must provide the public key of an initial dapp provider to manage the container. This action automatically creates a new dapp provider on the directory chain and adds it to the container voter set. The container voter set is crucial for approving new blockchain deployments and accepting new configurations. If needed, you can add additional members to this voter set, but only dapp providers are eligible to join. This guide outlines the steps to add a new dapp provider to the Directory Chain and your container voter set.

Prerequisites​

Process overview​

Follow these steps:

  1. The owner of the leased container requests a new dapp provider, which creates the dapp provider on the directory chain. This action also generates a proposal to add the new dapp provider to the container voter set.
  2. The container voter set reviews and approves the proposal generated in step 1.

Step 1: Request a new dapp provider​

As the owner of the leased container, execute the following command:

chr deployment voterset add-dapp-provider --container-id ${CONTAINER_NAME} --evm-auth ${LEASE_OWNER_EVM_ADDRESS} --pubkey ${NEW_PROVIDER}

Replace the placeholders with the following:

  • ${LEASE_OWNER_EVM_ADDRESS}: Your EVM address to authenticate the operation.
  • ${CONTAINER_NAME}: The name of your leased container.
  • ${NEW_PROVIDER}: The public key of the new dapp provider.

Step 2: Approve the proposal to add the dapp provider​

Next, the container voter set needs to take action. Use the chr deployment proposal commands to approve the automatically created proposal to add the new provider to the container voter set.