# Validator Guide

## Join Official Bridge Launch Governance

* Prepare the private key needed to sign(a.k.a **validating**) the correct cross-chain bridge
* Fork launch governance repository [\[LINK](https://github.com/orbit-chain/bridge-launch-governance)]
* Commit\&Push your governance information to the vault you wish to participate in 
* Send pull request

{% hint style="warning" %}
Do not expose your private key in information
{% endhint %}

## Launch Instance

{% content-ref url="validator-guide/hardware-specification" %}
[hardware-specification](https://bridge-docs.orbitchain.io/validator-guide/hardware-specification)
{% endcontent-ref %}

{% content-ref url="validator-guide/quick-start" %}
[quick-start](https://bridge-docs.orbitchain.io/validator-guide/quick-start)
{% endcontent-ref %}

## Expand Validating

### Vault

* Can participate in other vaults through the public [Github](https://github.com/orbit-chain/bridge-launch-governance).
* Launch another validator instance. Orbit Bridge is based on operating one validator in one vault.

{% hint style="warning" %}
The private key must use a different key from the existing vault.
{% endhint %}

### Chains

* There are basically 3 ways to access the chain
  * Using public node operator(like Ethereum's infura)
  * Directly operate the nodes of the chain(no need to mining block)
  * Some nodes provided by Ozys. Connection limited  by IP

{% hint style="info" %}
Each has its pros and cons. Using public node easy, but have potential stability, security risk. Running your own nodes is complex and expensive, but If you have a good understanding of the chain, can be obtain more secure, stability/
{% endhint %}

* Below are tips for each chain.

{% content-ref url="cross-chain-guide/icon" %}
[icon](https://bridge-docs.orbitchain.io/cross-chain-guide/icon)
{% endcontent-ref %}

{% content-ref url="cross-chain-guide/celo" %}
[celo](https://bridge-docs.orbitchain.io/cross-chain-guide/celo)
{% endcontent-ref %}