> For the complete documentation index, see [llms.txt](https://doc.cess.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.cess.network/ref/storage/node-discovery.md).

# Node Discovery

In CESS distributed storage system, two methods are implemented for node discovery: one based on a built-in [node discovery mechanism](https://docs.libp2p.io/concepts/discovery-routing/overview/) of `libp2p` library and another based on the CESS blockchain network implementation. This section mainly introduces how CESS-based storage nodes discover nodes within the blockchain.

As a storage node, it must have a CESS network identity - the CESS account (wallet account). It then issues a signed transaction `register` to become a storage node.

Before the storage node is activated, its identity is determined by the configuration file and the machine information. Upon registration, the node reports its identity to the blockchain network. Any node in the network can obtain identity information of other peer nodes and keep track of them to complete the node discovery process.


---

# 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://doc.cess.network/ref/storage/node-discovery.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.