# Run A Validator

We assume you have already created the Keystore file for your validator account following the [previous section.](/developers/run-a-node/run-a-validator-node/manager-account-and-validator-account.md)  You can run your validator node with the following command: 

```shell
geth --datadir /data/.kcc \
    --unlock 0x0000000000000000000000000000000000000000 \
    --password /data/.kcc/pass --mine 
```

{% hint style="info" %}
The command is similar to what we have seen in "[Run A Full Node](/developers/run-a-node/run-a-full-node.md)", except with some extra options:

The address after `--unlock` should be the address of your validator account. So you should replace `0x0000000000000000000000000000000000000000`  with your validator account. 

The path `/data/.kcc/pass` after `--password refers to a plain text file that contains the password of your Keystore file.`

`The --mine option tells the node try to validate and propose new blocks.` 
{% endhint %}

{% hint style="danger" %}
If you want to enable the HTTP and Websocket RPC servers on your validator node, you should never make them publicly accessible! Because that would make your validator account accessible through the RPC requests.  
{% endhint %}


---

# 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.kcc.io/developers/run-a-node/run-a-validator-node/run-a-validator.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.