> For the complete documentation index, see [llms.txt](https://zchains.gitbook.io/zchains-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zchains.gitbook.io/zchains-whitepaper/working-with-node/query-operator-info.md).

# Query operator information

### Prerequisites

This guide assumes you have followed the [Local Setup](/zchains-whitepaper/get-started/set-up-ibft-locally.md) or [guide on how to set up an IBFT cluster on the cloud](/zchains-whitepaper/get-started/set-up-ibft-on-the-cloud.md).

A functioning node is required in order to query any kind of operator information.

With the ZChains, node operators are in control and informed about what the node they're operating is doing.\
\
At any time, they can use the node information layer, built on top of gRPC, and get meaningful information - no log sifting required.

:::note

If your node isn't running on `127.0.0.1:8545` you should add a flag `--grpc-address <address:port>` to the commands listed in this document.

:::

### Peer information

#### Peers list

To get a complete list of connected peers (including the running node itself), run the following command:

```bash
polygon-edge peers list
```

This will return a list of libp2p addresses that are currently peers of the running client.

#### Peer status

For the status of a specific peer, run:

```bash
polygon-edge peers status --peer-id <address>
```

With the *address* parameter being the libp2p address of the peer.

### IBFT info

Lots of times, an operator might want to know about the state of the operating node in IBFT consensus.

Luckily, the Zchains provides an easy way to find this information.

#### Snapshots

Running the following command returns the most recent snapshot.

```bash
polygon-edge ibft snapshot
```

To query the snapshot at a specific height (block number), the operator can run:

```bash
polygon-edge ibft snapshot --num <block-number>
```

#### Candidates

To get the latest info on candidates, the operator can run:

```bash
polygon-edge ibft candidates
```

This command queries the current set of proposed candidates, as well as candidates that have not been included yet

#### Status

The following command returns the current validator key of the running IBFT client:

```bash
polygon-edge ibft status
```

### Transaction pool

To find the current number of transactions in the transaction pool, the operator can run:

```bash
polygon-edge txpool status
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://zchains.gitbook.io/zchains-whitepaper/working-with-node/query-operator-info.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.