# Misc commands

## Register validator with name, website and icon

See list of registered validators:

```sh
solana validator-info get
```

Set to you identity.json keypair:

```sh
solana config set -k identity.json
```

Publish your validator information:

{% code overflow="wrap" %}

```sh
solana validator-info publish "Validator name" -w "website" -i "icon URL" -k path/<identity keypair>
```

{% endcode %}

Note "-k" at the end which points to your identify.json including its path. This links your validator identity to the information you are providing. Your icon needs to be hosted.

Example:

{% code overflow="wrap" %}

```sh
solana validator-info publish "Jack's Ryzen Test Node" -w "https://x1.xyz" -i "https://x1.xyz/ryzen.jpg" -k .config/solana/identity.json
```

{% endcode %}

See validator info for specific validator:

```sh
solana validator-info get <Info address>
```

## Supply information

Get X1 supply (l for localnet):

```sh
solana -ul supply
```

Get Solana Supply (m for mainnet):

```sh
solana -um supply
```

Get stake history (shows stake history for 10 last epochs):

```sh
solana -ul stake-history
```

Epoch info:

```sh
solana epoch-info
```

Block production % per epoch

{% embed url="<http://xolana.xen.network:3232/api/epochs>" %}


---

# 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.x1.xyz/validating/misc-commands.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.