docs: purge references to rinkeby and ropsten (#26036)

docs/_developers/dns-discovery-setup.md

@@ -65,7 +65,7 @@ devp2p nodeset filter all-nodes.json -eth-network mainnet > mainnet.nodes.exampl
 
 The following filter flags are available:
 
-* `-eth-network ( mainnet | ropsten | rinkeby | goerli )` selects an Ethereum network.
+* `-eth-network ( mainnet | sepolia | goerli )` selects an Ethereum network.
 * `-les-server` selects LES server nodes.
 * `-ip <mask>` restricts nodes to the given IP range.
 * `-min-age <duration>` restricts the result to nodes which have been live for the

docs/_interface/Private-Network.md

@@ -26,7 +26,7 @@ geth --networkid 12345
 
 ### Choosing A Consensus Algorithm
 
-While the main network uses proof-of-work (PoW) to secure the blockchain, Geth also supports the the 'Clique' proof-of-authority (PoA) consensus algorithm as an alternative for private networks. Clique is strongly recommended for private testnets because PoA is far less resource-intensive than PoW. Clique is currently used as the consensus algorithm in public testnets such as [Rinkeby](https://www.rinkeby.io) and [Görli](https://goerli.net). The key differences between the consensus algorithms available in Geth are:
+While the main network uses proof-of-work (PoW) to secure the blockchain, Geth also supports the the 'Clique' proof-of-authority (PoA) consensus algorithm as an alternative for private networks. Clique is strongly recommended for private testnets because PoA is far less resource-intensive than PoW. The key differences between the consensus algorithms available in Geth are:
 
 #### Ethash
 
@@ -36,10 +36,8 @@ Geth's PoW algorithm, [Ethhash](https://ethereum.org/en/developers/docs/consensu
 
 Clique consensus is a PoA system where new blocks can be created by authorized 'signers' only. The clique consenus protocol is specified in [EIP-225][clique-eip]. The initial set of authorized signers is configured in the genesis block. Signers can be authorized and de-authorized using a voting mechanism, thus allowing the set of signers to change while the blockchain operates. Clique can be configured to target any block time (within reasonable limits) since it isn't tied to the difficulty adjustment.
 
-
 [clique-eip]: https://eips.ethereum.org/EIPS/eip-225
 
-
 ### Creating The Genesis Block
 
 Every blockchain starts with a genesis block. When Geth is run with default settings for the first time, it commits the Mainnet genesis to the database. For a private network, it is generally preferable to use a different genesis block. The genesis block is configured using a _genesis.json_ file whose path must be provided to Geth on start-up. When creating a genesis block, a few initial parameters for the private blockchain must be defined:

docs/_interface/consensus-clients.md

@@ -103,7 +103,5 @@ information can be found on the clients' respective documentation sites or in nu
 [execution-clients-link]: https://ethereum.org/en/developers/docs/nodes-and-clients/client-diversity/#execution-clients
 [launchpad-link]:https://launchpad.ethereum.org/
 [prater-launchpad-link]:https://prater.launchpad.ethereum.org/
-[kiln-launchpad-link]:https://kiln.launchpad.ethereum.org/
-[ropsten-launchpad-link]:https://ropsten.launchpad.ethereum.org/
 [e-org-link]: https://ethereum.org/en/developers/docs/nodes-and-clients/run-a-node/
 [checklist-link]:https://launchpad.ethereum.org/en/merge-readiness

docs/_rpc/ns-eth.md

@@ -85,6 +85,8 @@ call.
 
 #### Simple example
 
+**note that this example uses the Rinkeby testnet, which is now deprecated**
+
 With a synced Rinkeby node with RPC exposed on localhost (`geth --rinkeby --http`) we can
 make a call against the [Checkpoint
 Oracle](https://rinkeby.etherscan.io/address/0xebe8efa441b9302a0d7eaecc277c09d20d684540)