> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digitalasset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Self-hosted Validator Setup

> How to connect the DA Registry dApp UI to your validator.

The end goal is to be able to sign into the DA Registry dApp UI using an external wallet such as Console and Send.

## Connect the DA Registry dApp UI to your validator using the wallet gateway.

* Follow the instructions [here](https://docs.canton.network/integrations/wallet-gateway/operate/deploy)
* You will need to deploy a wallet-gateway instance and have the wallet-gateway config file properly configured

## Local Testing and Development

For local testing and developement, you can follow the quick start guide [here](https://docs.canton.network/integrations/wallet-gateway/quickstart)

## Third-party Wallet Providers (CIP-103 Compliant)

Below are the currently-supported third party wallet providers (CIP-103 compliant) that you can sign into the DA Registry Dapp UI with.

**Send wallet**

* Get the Send wallet chrome extension [here](https://chromewebstore.google.com/detail/send-connect/ldmohiccoioolenadmogclhoklmanpgi)
* Follow the steps to sign in / create an account
* Login to the DA Registry Dapp UI with Send

**Console wallet**

* Get the Console wallet chrome extension [here](https://consolewallet.io/).
* Follow steps to sign in / create an account
* Login to the DA Registry Dapp UI with Send

## Signing Providers

The Wallet Gateway does not have to hold private keys. Signing is delegated to a signing provider chosen per wallet. For more details about signing providers, see [here](https://docs.canton.network/integrations/wallet-gateway/operate/signing-providers).

### Some available providers:

* walletConnect / DFNS
* Fireblocks
* Blockdaemon