remove built-in Ropsten support (#4280)

* remove built-in Ropsten support

* link to ropsten shutdown-specific blog post

Co-authored-by: zah <zahary@status.im>

beacon_chain/networking/network_metadata.nim

@@ -203,11 +203,10 @@ elif const_preset == "mainnet":
   const
     mainnetMetadata* = eth2Network("shared/mainnet", mainnet)
     praterMetadata* = eth2Network("shared/prater", goerli)
-    ropstenMetadata* = mergeTestnet("ropsten-beacon-chain", ropsten)
     sepoliaMetadata* = mergeTestnet("sepolia", sepolia)
   static:
     for network in [
-        mainnetMetadata, praterMetadata, ropstenMetadata, sepoliaMetadata]:
+        mainnetMetadata, praterMetadata, sepoliaMetadata]:
       checkForkConsistency(network.cfg)
       doAssert network.cfg.CAPELLA_FORK_EPOCH == FAR_FUTURE_EPOCH
 
@@ -224,6 +223,9 @@ proc getMetadataForNetwork*(
       fatal "config.yaml not found for network", networkName
       quit 1
 
+  if networkName == "ropsten":
+    warn "Ropsten is unsupported; https://blog.ethereum.org/2022/11/30/ropsten-shutdown-announcement suggests migrating to Goerli or Sepolia"
+
   let metadata =
     when defined(gnosisChainBinary) and const_preset == "mainnet":
       case toLowerAscii(networkName)
@@ -242,8 +244,6 @@ proc getMetadataForNetwork*(
         mainnetMetadata
       of "prater", "goerli":
         praterMetadata
-      of "ropsten":
-        ropstenMetadata
       of "sepolia":
         sepoliaMetadata
       else:

docs/e2store.md

@@ -179,7 +179,7 @@ Each era is identified by when it ends. Thus, the genesis era is era `0`, follow
 
 `.era` file names follow a simple convention: `<config-name>-<era-number>-<era-count>-<short-historical-root>.era`:
 
-* `config-name` is the `CONFIG_NAME` field of the runtime configation (`mainnet`, `prater`, `ropsten`, `sepolia`, etc)
+* `config-name` is the `CONFIG_NAME` field of the runtime configation (`mainnet`, `prater`, `sepolia`, etc)
 * `era-number` is the number of the _first_ era stored in the file - for example, the genesis era file has number 0 - as a 5-digit 0-filled decimal integer
 * `short-era-root` is the first 4 bytes of the last historical root in the _last_ state in the era file, lower-case hex-encoded (8 characters), except the genesis era which instead uses the `genesis_validators_root` field from the genesis state.
   * The root is available as `state.historical_roots[era - 1]` except for genesis, which is `state.genesis_validators_root`

docs/the_nimbus_book/src/attestation-performance.md

@@ -34,7 +34,7 @@ The following options are available:
 
 Where:
 
-- The `network` can either be `mainnet`, `prater`, `ropsten` or `sepolia`
+- The `network` can be `mainnet`, `prater`, or `sepolia`
 
 - The default location of the `db`  is `build/data/shared_mainnet_0/db` for `mainnet`, `build/data/shared_prater_0/db` for `prater`, etc.
 

docs/the_nimbus_book/src/beacon-node-systemd.md

@@ -51,7 +51,7 @@ sudo systemctl edit nimbus_beacon_node.service
 
 The service file contains several options for controlling Nimbus. Important options include:
 
-* `Environment=NETWORK`: set this to `mainnet`, `prater` or `ropsten`, depending on which network you want to connect to
+* `Environment=NETWORK`: set this to `mainnet`, `prater` or `sepolia`, depending on which network you want to connect to
 * `Environment=WEB3_URL`: point this to your execution client - see the [Execution Client](./eth1.md) setup guide
 * `Environment=REST_ENABLED`: REST is used to interact with the beacon node, in particular when setting up a separate Validator Client - see the [REST API](./rest-api.md) guide
 * `Environment=METRICS_ENABLED`: Metrics are used for monitoring the node - see the [metrics](./metrics-pretty-pictures.md) setup guide