Documentation: add section for network configuration

Author: dannywillems

website/docs/node-runners/network-configuration.md

@@ -0,0 +1,156 @@
+---
+sidebar_position: 7
+title: Network Configuration
+description:
+  Learn about OpenMina's network configuration and how to contribute to the
+  default peer list
+slug: /node-runners/network-configuration
+---
+
+# Network Configuration
+
+This guide explains OpenMina's network configuration and how you can contribute
+to improving the network's connectivity.
+
+## Default Peers
+
+OpenMina includes hardcoded default peers for both mainnet and devnet networks
+to ensure reliable initial connectivity. These peers are defined in
+`core/src/network.rs:182` and `core/src/network.rs:265` respectively.
+
+### Mainnet Default Peers
+
+The mainnet configuration includes a curated list of reliable seed nodes
+operated by various community members and organizations. These peers help new
+nodes bootstrap their connection to the Mina Protocol network.
+
+### Devnet Default Peers
+
+The devnet configuration includes seed nodes specifically for development and
+testing purposes, allowing developers to connect to the test network.
+
+## Contributing to Default Peers
+
+The Mina community welcomes contributions to improve network connectivity by
+adding reliable seed nodes to the default peer lists.
+
+### Requirements for Peer Contribution
+
+To contribute a seed node to the default peer list, your node should meet these
+criteria:
+
+- **High Availability**: Node should have >99% uptime
+- **Stable Network**: Reliable internet connection with sufficient bandwidth
+- **Proper Configuration**: Correctly configured Mina Protocol node
+- **Long-term Commitment**: Willingness to maintain the node for extended
+  periods
+- **Network Security**: Secure server setup and regular maintenance
+
+### Contribution Process
+
+#### 1. Via OpenMina Repository
+
+For OpenMina-specific peer additions:
+
+1. Fork the [OpenMina repository](https://github.com/o1-labs/openmina)
+2. Edit the appropriate default peer list in `core/src/network.rs`:
+   - For mainnet: Update the `mainnet::default_peers()` function (line 265)
+   - For devnet: Update the `devnet::default_peers()` function (line 182)
+3. Add your peer's multiaddr in the format:
+   ```rust
+   "/ip4/YOUR_IP/tcp/PORT/p2p/YOUR_PEER_ID",
+   ```
+4. Submit a pull request with:
+   - Description of your node setup
+   - Expected uptime and maintenance commitment
+   - Contact information for node operator
+
+#### 2. Via Official Seeds Repository
+
+For broader Mina Protocol peer contributions, consider using the official seeds
+repository:
+
+1. Visit the
+   [Mina Foundation Seeds Repository](https://github.com/o1-labs/seeds)
+2. Follow their contribution guidelines:
+   - Fork the repository
+   - Add your seed to the appropriate network list file
+   - Ensure all pre-commit checks pass
+   - Submit a pull request with detailed explanation
+   - Wait for maintainer review and potential merge
+
+The seeds repository maintains the canonical list of seed nodes accessible at
+`https://bootnodes.minaprotocol.com/networks/mainnet.txt`.
+
+### Peer Address Format
+
+Peer addresses use the multiaddr format:
+
+```
+/dns4/hostname/tcp/port/p2p/peer_id
+/ip4/ip_address/tcp/port/p2p/peer_id
+```
+
+Where:
+
+- `hostname` or `ip_address`: Your node's network address
+- `port`: The libp2p port (commonly 8302 for mainnet, 10003 for devnet)
+- `peer_id`: Your node's unique peer identifier
+
+### Testing Your Contribution
+
+Before submitting a peer contribution:
+
+1. **Verify Connectivity**: Ensure your node is accessible from the internet
+2. **Test Peer Discovery**: Confirm other nodes can discover and connect to
+   yours
+3. **Check Network Compatibility**: Verify your node works with both OCaml and
+   Rust implementations
+4. **Monitor Performance**: Ensure stable performance under normal network load
+
+### Node Operation Best Practices
+
+When running a seed node:
+
+- **Monitor Uptime**: Use monitoring tools to track node availability
+- **Regular Updates**: Keep your node software up to date
+- **Resource Management**: Ensure adequate CPU, memory, and bandwidth
+- **Security Measures**: Implement proper firewall and security configurations
+- **Documentation**: Maintain documentation of your node's configuration
+
+### Community Resources
+
+- **GitHub Discussions**: Join discussions on the OpenMina repository
+- **Discord**: Connect with the community on the
+  [Mina Protocol Discord](https://discord.com/channels/484437221055922177/1290662938734231552)
+- **Forums**: Participate in
+  [Mina Protocol Forums](https://forums.minaprotocol.com/)
+
+## Advanced Network Configuration
+
+### Custom Peer Lists
+
+While OpenMina uses default peers for initial connectivity, you can configure
+your node to use custom peer lists by modifying the network configuration or
+using command-line options during node startup.
+
+### Network Monitoring
+
+Monitor your node's network connectivity through:
+
+- OpenMina's built-in dashboard
+- Peer connection metrics
+- Network synchronization status
+
+## Troubleshooting
+
+### Common Connectivity Issues
+
+- **Firewall Blocking**: Ensure the libp2p port is open
+- **NAT Configuration**: Configure port forwarding if behind NAT
+- **Peer Discovery**: Check if your node appears in other nodes' peer lists
+- **Network Segmentation**: Verify connectivity to multiple network regions
+
+For additional troubleshooting, refer to the
+[troubleshooting documentation](../troubleshooting) or reach out to the
+community for support.