​

Onboarding (Primary Validator)

The onboarding process consists of the following high-level steps.

​

1. Choose a Third Node Operator

• Select a third-party node operator that will host parties on an additional covalidating node.

​

2. Configure the DAR Repository

• Create and configure access to a shared repository from which all participating covalidators synchronize DARs. Commit key DARs to this repository.

Important Configuring a GitHub App requires GitHub Organization Owner permissions.

​

Create a GitHub Repo

• Create a GitHub repo that will hold all your DARs
• Separate by directories aligned with environments (DevNet, TestNet, MainNet)

​

Install GitHub Apps from URLs provided by Covalidators

• Paste in URL provided by each Covalidator
• Choose Configure from the GitHub UI (login as appropriate)
• Choose GitHub Organization to install to — the organization where you have created your DAR repo.
• Grant Repository Access to your DAR repository
• Take note of the Installation ID from the URI and share this with the covalidator — it is the last portion of the URL (https://github.com/organizations/YOURORG/settings/installations/INSTALLATION_ID)
• Provide the details of your repo to your partner / DA
  • Installation ID
  • GitHub Org Name
  • GitHub Repo Name
  • Path to DARs (by environment)

​

3. Configure your Validator Node

• Create / configure the validator node which you will use as your primary node.

​

Upload and Vet DARs

• Ensure all DARs are uploaded from your DAR Repository. Vet the DARs which should be active on this node.

​

4. Exchange Configuration Details

• Exchange DAR repository details and your participant ID details so that each co-validator can be configured correctly.
• Additionally, take note of the participant IDs of the covalidating nodes, as you will need these details when onboarding parties.

​

5. Configure Party Topology

• Once all validators are online and configured, create a topology transaction to multi-host a party — covalidating nodes running the covalidation service will automatically approve the transaction if it matches the agreed-upon topology.

​

6. Validate Transactions

• When a multi-hosted party submits a transaction, confirmation nodes independently validate the transaction against the synchronized DARs before confirming it.

​

7. Manage Ongoing Configuration

• As applications evolve, new DARs and topology changes can be introduced through the established governance process.