WIP

Author: coderofstuff

README.md

@@ -9,6 +9,10 @@ Your feedback, contributions, and issue reports will be integral to evolving thi
 
 The default branch of this repository is `master` and new contributions are constantly merged into it. For a stable branch corresponding to the latest stable release please pull and compile the `stable` branch. 
 
+## 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 <a>this node specification and testing guide</a>.
+
 ## Installation
   <details>
   <summary>Building on Linux</summary>

docs/crescendo-testing.md

@@ -0,0 +1,67 @@
+# Kaspa Testnet 10 (TN10) – 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.
+
+
+**Important Note:**  
+- Version [0.17.1](https://github.com/kaspanet/rusty-kaspa/releases/tag/v0.17.1) does **not** support TN11. Some participants should keep TN11 nodes running on the latest stable release or `stable` branch until TN10’s performance is proven stable.
+
+---
+
+## Recommended Hardware Specifications
+
+- **Minimum**:  
+  - 8 CPU cores  
+  - 16 GB RAM  
+  - 256 GB SSD  
+  - 5 MB/s (or ~40 Mbit/s) network bandwidth
+
+- **Preferred for Higher Performance**:  
+  - 12–16 CPU cores  
+  - 32 GB RAM  
+  - 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.
+
+// TODO: Recommend slighly higher specs that min for pools
+
+---
+
+## 1. Install & Run Your Node
+
+1. **Obtain Kaspa v1.0.0 binaries**  
+    Download and extract the official [1.0.0 release](https://github.com/kaspanet/rusty-kaspa/releases/tag/v1.0.0), or build from the `master` branch by following the instructions in the project README.
+
+2. **Launch the Node**  
+    ```
+    kaspad --utxoindex
+    ```
+
+    *(If running from source code:)*  
+    ```
+    cargo run --bin kaspad --release -- --utxoindex
+    ```
+
+    To run on testnet, simply add `--testnet` at the end. For example:
+
+    ```
+    kaspad --utxoindex --testnet
+    ```
+
+Leave this process running. Closing it will stop your node.
+
+- **Advanced Command-Line Options**:
+  - `--rpclisten=0.0.0.0` to listen for RPC connections on all network interfaces (public RPC).
+  - `--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.
+  - `--loglevel=kaspa_grpc_server=warn` for suppressing most RPC connect/disconnect log reports.
+  - `--ram-scale=3.0` for increasing cache size threefold (relevant for utilizing large RAM; can be set between 0.1 and 10).
+
+---
+
+## Mining on your node
+
+1. Notes about warns on mainnet for outdated miner
+