# Run Validator Node

Before setting up a validator node, make sure to have completed the [Node Setup](/ggez1-chain/nodes-and-validators/node-setup.md) guide.

## Create Account

We will create an account to control the validator.

```
ggezchaind keys add account_name
```

If you have already have an account add `--recover` flag to previous command.

{% hint style="info" %}
Activate the account by sending tokens to it.
{% endhint %}

## Create Validator

create a `validator.json` file:

```
{
  "pubkey": {
    "@type": "/cosmos.crypto.ed25519.PubKey",
    "key": "Pc1g/vSn3nT1BA/R6FdfAjlze1WBkU6IaAaNzB92ckw="
  },
  "amount": "<amount>uggez1",
  "moniker": "myvalidator",
  "website": "https://validator_website",
  "commission-rate": "0.1",
  "commission-max-rate": "0.2",
  "commission-max-change-rate": "0.01",
  "min-self-delegation": "1"
}
```

Now to create the validator.

```
ggezchaind tx staking create-validator path/to/validator.json --from account_name --gas auto --gas-prices 0.4uggez1 --gas-adjustment 1.5
```

Now if transaction processed successfully you can check your validator if it accepted.

```
ggezchaind q staking validators
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ggez.one/ggez1-chain/nodes-and-validators/run-validator-node.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.