# Public Peer Nodes Our blockchain network maintains a set of public peer nodes that serve as reliable entry points for network participation. These well-known nodes are preconfigured directly in the software's source code, meaning that in most cases, you won't need to manually add them to your configuration file. The software automatically establishes connections with these trusted peers when you start your node. For advanced users who wish to customize their peer connections or need to reference the default nodes, these nodes are configured using the 'addnode' parameter in the configuration file. Our development team manages and maintains these nodes, ensuring they remain stable and continuously synchronized with the latest blockchain state. ### Configuration Details While manual configuration is typically unnecessary due to the built-in node addresses, you may want to know the addresses of our public peers for reference or troubleshooting. [Our network maintains five public nodes](http://status.getlynx.io/) for redundancy and optimal network distribution. A connection to at least three nodes ensures reliable network participation. Here are the addresses of our public peers: {% code title="\~/.lynx/lynx.conf" %} ``` addnode=node1.getlynx.io addnode=node2.getlynx.io addnode=node3.getlynx.io addnode=node4.getlynx.io addnode=node5.getlynx.io ``` {% endcode %} ### Node Management Our development team [actively monitors these public nodes](http://status.getlynx.io/) to maintain their reliability. We regularly: * Update node software to the latest stable version * Monitor network connectivity and performance * Ensure high uptime and availability * Verify blockchain synchronization status This ongoing maintenance helps ensure that new nodes can reliably join the network and existing nodes can maintain robust peer connections. The automatic inclusion of these peer addresses in the software simplifies the setup process for most users while maintaining the flexibility needed for advanced configurations. --- # 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.getlynx.io/lynx-administration/lynx-nodes.md?ask= ``` 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.