# Fallback plan for validator updater

### 1. Fallback plan when gnosissafe is down

Let's assume that the Band's rest endpoints and Ethereum RPC are working fine. Then, we must prepare a script for generating a message and sign it before sending it to the Gnosis contract. Of course, the signing team must cooperate when the Gnosissafe is down to help the submitter gather signatures.
- Create a script that is able to generate a message and sign using a ledger
- The script should also be able to send a tx to the target chain

### 2. Fallback plan when Band's scan is down

According to what we have consulted with the Chain team, there will be two endpoints for retrieving the Band’s validators from the mainnet [Laozi1](https://laozi1.bandchain.org/api/bandchain/evm-validators) and [Laozi4](https://laozi4.bandchain.org/api/bandchain/evm-validators). We should add those endpoints for redundancy to make the system more resilient. In addition, we need to throw an error if both of the endpoints are down. If we find that the endpoints are down often until we start to see it as a problem, then we will consult the Chain team.
- add more endpoints
- throw an error to the discord if both endpoints are down

### 3. Fallback plan when Client's scan is down

Let's assume we are using EOA as the owner.
- Use the script from 1.
- Use remix to interact with the Bridge contract
- But if the RPC is down, then we should contact our partner