Lynx Blockchain
  • Welcome
  • Technical Evolution and Architecture Overview
  • History of Lynx
    • Evolution of a Blockchain
    • Hybrid Proof of Work (HPoW) Protocol
    • Pioneering Blockchain Data Storage
    • Evolution to Proof of Stake
    • Next Generation Data Storage Architecture
    • Preserving Knowledge
  • Lynx Core
    • Hardware and System Requirements
    • Lynx Dynamics
    • Open Source
    • Core Parameters and Strategy
    • Sustainability
    • Circulating Supply Analysis
    • Locked Addresses
    • Data Storage
      • auth
      • fetch
      • fetchall
      • store
      • status
      • list
    • Understanding the Encryption Option
    • Understanding Lynx Staking Wait Times
    • Understanding Asset Retrieval Times
    • Understanding Block Time Targeting in the Lynx Blockchain
    • Understanding the Lynx Blockchain Statistics Report
  • Lynx Administration
    • Public Peer Nodes
    • Understanding Blockchain Bootstrap Files
      • Bootstrap Extraction Script
      • Bootstrap Creation Script
    • How to Sweep a Lynx Wallet
    • Enable/Disable Staking
  • Clevver
    • Revolutionizing Digital Preservation
    • Permanent Storage for Digital Assets
    • Permanent Digital Archives for Journalism
    • How did Clevver originate?
    • Shortened URL Support
    • Assigning Tags to Assets
    • How to delete content
    • Clevver Terms of Service Agreement
  • Clevver API
    • Public Methods
      • Batches
      • Files
      • User
  • ElectrumX
    • Lynx ElectrumX nodes
    • Build Script Details
  • External Links
    • Lynx Explorer
    • Lynx Github
    • Lynx Uptime Report
    • Clevver Website
  • Lynx Bootstraps
  • Wallet Links
    • Komodo Wallet
    • Wally.id Wallet
    • Lynx Paper Wallet
  • Social Links
    • Lynx Discord
    • Lynx on Bluesky
    • Clevver on Bluesky
  • Exchange Links
    • FreiXLite (LYNX/LTC)
  • FreiExchange (LYNX/BTC)
  • Komodo Wallet (SWAP)
  • XredX (LYNX/LTC)
  • XredX (LYNX/DOGE)
  • XredX (LYNX/IL8P)
Powered by GitBook
On this page
  • Configuration Details
  • Node Management
  1. Lynx Administration

Public Peer Nodes

Published: December 2024 | Last updated: April 2025

PreviousUnderstanding the Lynx Blockchain Statistics ReportNextUnderstanding Blockchain Bootstrap Files

Last updated 20 days ago

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. 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:

~/.lynx/lynx.conf
addnode=node1.getlynx.io
addnode=node2.getlynx.io
addnode=node3.getlynx.io
addnode=node4.getlynx.io
addnode=node5.getlynx.io

Node Management

Our development team 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.

Our network maintains five public nodes
actively monitors these public nodes
Page cover image