[Polkadot Wiki Migration] Set up a Bootnode

.snippets/code/infrastructure/general/bootnode.conf

@@ -0,0 +1,19 @@
+server {
+       listen       30312 ssl http2 default_server;
+       server_name  dot-bootnode.stakeworld.io;
+       root         /var/www/html;
+
+       ssl_certificate "<your_cert";
+       ssl_certificate_key "<your_key>";
+
+       location / {
+         proxy_buffers 16 4k;
+         proxy_buffer_size 2k;
+         proxy_pass http://localhost:30311;
+         proxy_http_version 1.1;
+         proxy_set_header Upgrade $http_upgrade;
+         proxy_set_header Connection "Upgrade";
+         proxy_set_header Host $host;
+   }
+
+}

infrastructure/general/.pages

@@ -1,3 +1,4 @@
 title: General Infrastructure
 nav:
   - index.md
+  - 'Set Up a Bootnode': 'setup-bootnode.md'

infrastructure/general/setup-bootnode.md

@@ -0,0 +1,86 @@
+---
+title: Set Up a Bootnode
+description: Learn how to configure and run a bootnode for Polkadot, including P2P, WS, and secure WSS connections with network key management and proxies.
+---
+
+# Set Up a Bootnode
+
+## Introduction
+
+Bootnodes are essential for helping blockchain nodes discover peers and join the network. When a node starts, it needs to find other nodes, and bootnodes provide an initial point of contact. Once connected, a node can expand its peer connections and play its role in the network, like participating as a validator. This guide will walk you through setting up a Polkadot bootnode, configuring P2P, WebSocket (WS), secure WSS connections, and managing network keys. You’ll also learn how to test your bootnode to ensure it is running correctly and accessible to other nodes.
+
+## Prerequisites
+
+Before you start, you need to have the following prerequisites:
+
+- A working Polkadot (`polkadot`) installation
+- NGINX
+- A VPS, or other dedicated server setup
+
+## Accessing the Bootnode
+
+To connect with other nodes in the network, bootnodes must be accessible through three key channels:
+
+- **P2P** - a direct peer-to-peer connection, set by `--listen-addr /ip4/0.0.0.0/tcp/<port>`. This is not enabled by default on non-validator nodes like archive RPC nodes
+- **P2P/WS** - a WebSocket (WS) connection, also configured via `--listen-addr`
+- **P2P/WSS** - a secure WebSocket (WSS) connection using SSL, often required for light clients. An SSL proxy is needed, as the node itself cannot handle certificates
+
+## Node Key
+
+A node key is the ED25519 key that `libp2p` to assign an identity/peer ID to your node. Generating a known node key for a bootnode is crucial, as this way you have a consistent key that can be placed in chain specifications as a reliable bootnode.
+
+Starting a node creates its node key in the `chains/<chain>/network/secret_ed25519` file.
+
+You can create a node key using:
+
+ ```
+ polkadot key generate-node-key
+ ``` 
+
+This key can be used in the startup command line.
+
+It is *essential* you backup the node key, especially if it gets included in the `polkadot` binary because it gets hardcoded in the binary and needs to be recompiled to change.
+
+## Running the Bootnode
+
+A boot node can be run as follows:
+
+ ```sh
+ polkadot --chain polkadot \
+ --name dot-bootnode \
+ --listen-addr /ip4/0.0.0.0/tcp/30310 \
+ --listen-addr /ip4/0.0.0.0/tcp/30311/ws
+ ```
+
+This would have the p2p on port 30310 and p2p/ws on port 30311. For the p2p/wss port, a proxy must set up a DNS name and a corresponding certificate. The following example is for the popular nginx server and enables p2p/wss on port 30312 by adding a proxy to the p2p/ws port 30311:
+
+_Located in /etc/nginx/sites-enabled/dot-bootnode_
+
+```conf
+--8<-- 'code/infrastructure/general/bootnode.conf'
+```
+
+## Testing Bootnode Connection
+
+If the preceding node is running with DNS name `dot-bootnode.stakeworld.io`, which contains a proxy with a valid certificate and node-id `12D3KooWAb5MyC1UJiEQJk4Hg4B2Vi3AJdqSUhTGYUqSnEqCFMFg` then the following commands should give you a: `syncing 1 peers`.
+
+!!!tip
+    You can add `-lsub-libp2p=trace` on the end to get libp2p trace logging for debugging purposes.
+
+### P2P
+
+```bash
+polkadot --chain polkadot --base-path /tmp/node --name "Bootnode testnode" --reserved-only --reserved-nodes "/dns/dot-bootnode.stakeworld.io/tcp/30310/p2p/12D3KooWAb5MyC1UJiEQJk4Hg4B2Vi3AJdqSUhTGYUqSnEqCFMFg" --no-hardware-benchmarks
+```
+
+### P2P/WS
+
+```bash
+polkadot --chain polkadot --base-path /tmp/node --name "Bootnode testnode" --reserved-only --reserved-nodes "/dns/dot-bootnode.stakeworld.io/tcp/30311/ws/p2p/12D3KooWAb5MyC1UJiEQJk4Hg4B2Vi3AJdqSUhTGYUqSnEqCFMFg" --no-hardware-benchmarks
+```
+
+### P2P/WSS
+
+```bash
+polkadot --chain polkadot --base-path /tmp/node --name "Bootnode testnode" --reserved-only --reserved-nodes "/dns/dot-bootnode.stakeworld.io/tcp/30312/wss/p2p/12D3KooWAb5MyC1UJiEQJk4Hg4B2Vi3AJdqSUhTGYUqSnEqCFMFg" --no-hardware-benchmarks
+```