Adding Grandine to CL client pages and updating Rocket Pool Guide link

networking/port-forwarding.md

@@ -22,6 +22,7 @@ Below are a list of the default ports that the software(s) are set to listen on.
 | [Nimbus](https://nimbus.guide/networking.html)                                                              | 9000 TCP/UDP         |
 | [Prysm](https://docs.prylabs.network/docs/prysm-usage/p2p-host-ip#incoming-p2p-connection-prerequisites)    | 12000 UDP, 13000 TCP |
 | [Teku](https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/#p2p-port)                                  | 9000 TCP/UDP         |
+| [Grandine](https://docs.grandine.io/beacon_node_api.html)                                                   | 9000 TCP/UDP         |
 
 If your node is running and the port(s) have been forwarded, you can use an online tool [such as this one](https://www.yougetsignal.com/tools/open-ports/) to check whether the ports are forwarded correctly.
 

tutorials/solo-staking-guides.md

@@ -4,7 +4,7 @@ This is a list of high quality staking guides that are recommended on [ethereum.
 
 - [CoinCashew's Ethereum 2.0 Guide - Linux (CLI) ↗](https://www.coincashew.com/coins/overview-eth/guide-or-how-to-setup-a-validator-on-eth2-mainnet)
 - [Somer Esat - Linux (CLI) ↗](https://github.com/SomerEsat/ethereum-staking-guides)
-- [Rocket Pool Node Operators - Linux, macOS (CLI) ↗](https://rocketpool.net/node-operators)
+- [Rocket Pool Node Operators - Linux, macOS (CLI) ↗](https://docs.rocketpool.net/guides/node/responsibilities)
 
 It's critically important for the health and long term sustainability of Ethereum that there is a diverse and balanced client ecosystem. Multiple, independently developed and maintained clients exist because client diversity makes the network more resilient to attacks and bugs. Multiple clients is a strength unique to Ethereum - other blockchains rely on the infallibility of a single client. However, it is not enough simply to have multiple, clients available, they have to be adopted by the community and the total active nodes distributed relatively evenly across them.
 

validator-clients/consensus-clients.md

@@ -9,7 +9,7 @@ Consensus clients run the Beacon Chain and provide a [proof-of-stake (PoS)](../s
 
 Consensus clients all follow the same [specification ↗](https://github.com/ethereum/consensus-specs). If a client doesn't follow this spec it won't be able to come to consensus with the rest of the network.
 
-<table><thead><tr><th width="161">Client</th><th width="185">Documentation</th><th width="168">GitHub</th><th width="193">Discord</th></tr></thead><tbody><tr><td><strong>Lighthouse</strong></td><td><a href="https://lighthouse-book.sigmaprime.io/">Link ↗</a></td><td><a href="https://github.com/sigp/lighthouse">Link ↗</a></td><td><a href="https://discord.gg/gdq27tnKSM">Link ↗</a></td></tr><tr><td><strong>Lodestar</strong></td><td><a href="https://chainsafe.github.io/lodestar/">Link ↗</a></td><td><a href="https://github.com/ChainSafe/lodestar">Link ↗</a></td><td><a href="https://discord.com/invite/yjyvFRP">Link ↗</a></td></tr><tr><td><strong>Nimbus</strong></td><td><a href="https://status-im.github.io/nimbus-eth2/intro.html">Link ↗</a></td><td><a href="https://github.com/status-im/nimbus-eth2">Link ↗</a></td><td><a href="https://discord.gg/aTDcbTG2gQ">Link ↗</a></td></tr><tr><td><strong>Prysm</strong></td><td><a href="https://docs.prylabs.network/docs/getting-started">Link ↗</a></td><td><a href="https://github.com/prysmaticlabs/prysm">Link ↗</a></td><td><a href="https://discord.gg/GVM5TJwzkU">Link ↗</a></td></tr><tr><td><strong>Teku</strong></td><td><a href="https://docs.teku.consensys.net/en/stable/">Link ↗</a></td><td><a href="https://github.com/ConsenSys/teku">Link ↗</a></td><td><a href="https://discord.gg/trQ378WCp4">Link ↗</a><br>(#teku channel)</td></tr></tbody></table>
+<table><thead><tr><th width="161">Client</th><th width="185">Documentation</th><th width="168">GitHub</th><th width="193">Discord</th></tr></thead><tbody><tr><td><strong>Lighthouse</strong></td><td><a href="https://lighthouse-book.sigmaprime.io/">Link ↗</a></td><td><a href="https://github.com/sigp/lighthouse">Link ↗</a></td><td><a href="https://discord.gg/gdq27tnKSM">Link ↗</a></td></tr><tr><td><strong>Lodestar</strong></td><td><a href="https://chainsafe.github.io/lodestar/">Link ↗</a></td><td><a href="https://github.com/ChainSafe/lodestar">Link ↗</a></td><td><a href="https://discord.com/invite/yjyvFRP">Link ↗</a></td></tr><tr><td><strong>Nimbus</strong></td><td><a href="https://status-im.github.io/nimbus-eth2/intro.html">Link ↗</a></td><td><a href="https://github.com/status-im/nimbus-eth2">Link ↗</a></td><td><a href="https://discord.gg/aTDcbTG2gQ">Link ↗</a></td></tr><tr><td><strong>Prysm</strong></td><td><a href="https://docs.prylabs.network/docs/getting-started">Link ↗</a></td><td><a href="https://github.com/prysmaticlabs/prysm">Link ↗</a></td><td><a href="https://discord.gg/GVM5TJwzkU">Link ↗</a></td></tr><tr><td><strong>Teku</strong></td><td><a href="https://docs.teku.consensys.net/en/stable/">Link ↗</a></td><td><a href="https://github.com/ConsenSys/teku">Link ↗</a></td><td><a href="https://discord.gg/trQ378WCp4">Link ↗</a><br>(#teku channel)</td></tr><tr><td><strong>Grandine</strong></td><td><a href="https://docs.grandine.io/">Link ↗</a></td><td><a href="https://github.com/grandinetech/grandine">Link ↗</a></td><td><a href="https://discord.gg/H9XCdUSyZd">Link ↗</a></td></tr></tbody></table>
 
 ### Lighthouse
 
@@ -39,3 +39,6 @@ Teku offers very flexible deployment options. The beacon node and validator clie
 
 Teku is written in Java and is Apache 2.0 licensed. It is developed by the Protocols team at ConsenSys that is also responsible for Besu and Web3Signer.
 
+### Grandine
+
+Grandine is a consensus client implementation, written in Rust under the GPL-3.0 license. It is maintained by the Grandine Core Team and is fast, high-performance and lightweight. It fits a wide range of stakers from solo stakers running on low-resource devices such as Raspberry Pi to large institutional stakers running tens of thousands of validators.