> For the complete documentation index, see [llms.txt](https://geodb.gitbook.io/odin-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://geodb.gitbook.io/odin-protocol/becoming-odin-validator.md).

# Becoming ODIN Validator

### Becoming a Validator

To become a validator, you must submit a `create-validator` transaction to the network.  It is recommended to wait for your node to be fully synced before running this transaction.  You will need to stake some or all of your tokens to improve your odds of being selected as a validator. First, open an interactive shell inside the container and pass the four important environment variables you've created into the container: 

```
docker exec -e STAKE=$STAKE -e ADDRESS=$ADDRESS -e MONIKER=$MONIKER -e CHAIN=$CHAIN -it node /bin/bash
```

Then, run the following command:

```
bandd tx staking create-validator \
--amount $STAKE \
--commission-max-change-rate 0.01 \
--commission-max-rate 0.2 \
--commission-rate 0.1 \
--from $ADDRESS \
--min-self-delegation 1 \
--moniker $MONIKER \
--pubkey $(bandd tendermint show-validator) \
--chain-id $CHAIN \
--node http://34.77.171.169:26657
```

You will be asked to verify the transaction before it is submitted to the network. After you've done that, `exit` the container's shell.

#### Making Sure it Worked

To verify that you have successfully become a staked validator, you can query the network: 

```
docker exec -it node bandd query staking validators --chain-id $CHAIN --node http://34.77.171.169:26657
```

 This command will return a list of staking validators. If the moniker you chose appears, then you have successfully become a staked validator and your node is eligible to be selected by users to validate blocks.