WIP4

Author: coderofstuff

docs/crescendo-guide.md

@@ -1,8 +1,6 @@
 # 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 at DAA Score `110,165,000` which is roughly `2025-05-05 1500 UTC`.
-
----
+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. The hardfork is scheduled to activate on mainnet at DAA Score `110,165,000` which is roughly `2025-05-05 1500 UTC`.
 
 ## Recommended Hardware Specifications
 
@@ -22,8 +20,6 @@ While the minimum specs suffice to sync and maintain a TN10 node with the accele
 
 If you are a pool operator, it is _strongly recommended_ that you pick specs that are closer to the preferred specifications above.
 
----
-
 ## Running Your Node
 
 1. **Obtain Kaspa v1.0.0 binaries**  
@@ -56,8 +52,6 @@ Leave this process running. Closing it will stop your node. If you have other fl
   - `--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 and Preparation for Crescendo
 
 Crescendo introduces a new field in transactions, `mass`, which needs to be preserved from the template that you get from `GetBlockTemplate` and passed back when you submit your mined block via `SubmitBlock`.