WIP3

Author: coderofstuff

README.md

@@ -11,7 +11,7 @@ The default branch of this repository is `master` and new contributions are cons
 
 ## The Crescendo Hardfork
 
-The Crescendo Hardfork which will transition the network to 10BPS is scheduled to occur in mainnet on `2025-05-05 1500 UTC` at DAA Score `110,165,000`. You can participate in testing the hardfork on mainnet (prior to activation) or on the already activated testnet by following [this node specification and testing guide](docs/crescendo.md).
+The Crescendo Hardfork which will transition the network to 10BPS is scheduled to occur in mainnet on `2025-05-05 1500 UTC` at DAA Score `110,165,000`. You can participate in testing the hardfork on mainnet (prior to activation) or on the already activated testnet by following [this node specification and testing guide](docs/crescendo-guide.md).
 
 ## Installation
   <details>

docs/crescendo.md renamed to docs/crescendo-guide.md

@@ -1,6 +1,6 @@
-# Kaspa Testnet 10 (TN10) – Crescendo Hardfork Node Setup Guide
+# Kaspa Crescendo Hardfork Node Setup Guide
 
-Kaspa is about to take a significant leap with the **Crescendo Hardfork**, as detailed in [KIP14](https://github.com/kaspanet/kips/blob/master/kip-0014.md), transitioning from 1 to 10 blocks per second. It is scheduled to activate on mainnet on 2025-05-05 1500 UTC at DAA Score 110,165,000.
+Kaspa is about to take a significant leap with the **Crescendo Hardfork**, as detailed in [KIP14](https://github.com/kaspanet/kips/blob/master/kip-0014.md), transitioning from 1 to 10 blocks per second. It is scheduled to activate on mainnet at DAA Score `110,165,000` which is roughly `2025-05-05 1500 UTC`.
 
 ---
 
@@ -18,7 +18,9 @@ Kaspa is about to take a significant leap with the **Crescendo Hardfork**, as de
   - 512 GB SSD  
   - Higher network bandwidth for robust peer support
 
-While the minimum specs suffice to sync and maintain a TN10 node with the accelerated 10 bps, increasing CPU cores, RAM, storage, and bandwidth allows your node to serve as a stronger focal point on the network. This leads to faster initial block download (IBD) for peers syncing from your node and provides more leeway for future storage growth and optimization. If you are a pool operator, it is recommended that you pick specs that are closer to the preferred specifications above.
+While the minimum specs suffice to sync and maintain a TN10 node with the accelerated 10 bps, increasing CPU cores, RAM, storage, and bandwidth allows your node to serve as a stronger focal point on the network. This leads to faster initial block download (IBD) for peers syncing from your node and provides more leeway for future storage growth and optimization.
+
+If you are a pool operator, it is _strongly recommended_ that you pick specs that are closer to the preferred specifications above.
 
 ---
 
@@ -46,7 +48,8 @@ While the minimum specs suffice to sync and maintain a TN10 node with the accele
 Leave this process running. Closing it will stop your node. If you have other flags that you use for your current node, you may continue to use those.
 
 - **Advanced Command-Line Options**:
-  - `--rpclisten=0.0.0.0` to listen for RPC connections on all network interfaces (public RPC).
+  - `--disable-upnp` if you don't want your node to be automatically publicly connectable (if your router supports UPnP). Recommended for pools and exchanges.
+  - `--rpclisten=0.0.0.0` to listen for RPC connections on all network interfaces (public RPC). Use `--rpclisten=127.0.0.1` if you are running your pool/exchange software on the same machine
   - `--rpclisten-borsh` for local borsh RPC access from the `kaspa-cli` binary.
   - `--unsaferpc` for allowing P2P peer query and management via RPC (recommended to use only if **not** exposing RPC publicly).
   - `--perf-metrics --loglevel=info,kaspad_lib::daemon=debug,kaspa_mining::monitor=debug` for detailed performance logs.