clients: remove openethereum as its deprecated (ethereum#932)

Author: spencer-tb

clients/openethereum/Dockerfile

@@ -98,8 +98,8 @@ container:
 On startup, the entry point script must first load the genesis block and state into the
 client implementation from `/genesis.json`. To do this, the script needs to translate from
 Geth genesis format into a format appropriate for the specific client implementation. The
-translation is usually done using a jq script. See the [openethereum genesis
-translator][oe-genesis-jq], for example.
+translation is usually done using a jq script. See the [go-ethereum genesis
+translator][geth-genesis-jq], for example.
 
 After the genesis state, the client should import the blocks from `/chain.rlp` if it is
 present, and finally import the individual blocks from `/blocks` in file name order. The
@@ -165,7 +165,7 @@ For the server role, the following additional variables should be supported:
 [LES]: https://github.com/ethereum/devp2p/blob/master/caps/les.md
 [geth-docker]: ../clients/go-ethereum/Dockerfile
 [hive-client-yaml]: ./commandline.md#client-build-parameters
-[oe-genesis-jq]: ../clients/openethereum/mapper.jq
+[geth-genesis-jq]: ../clients/go-ethereum/mapper.jq
 [EIP-155]: https://eips.ethereum.org/EIPS/eip-155
 [EIP-606]: https://eips.ethereum.org/EIPS/eip-606
 [EIP-607]: https://eips.ethereum.org/EIPS/eip-607

clients/openethereum/chain.json

@@ -29,10 +29,10 @@ simulation, use the following command:
 
     ./hive --sim <simulation> --client <client(s) you want to test against>
 
-For example, if you want to run the `discv4` test against geth and openethereum, here is
+For example, if you want to run the `discv4` test against geth, here is
 how the command would look:
 
-    ./hive --sim devp2p --sim.limit discv4 --client go-ethereum,openethereum
+    ./hive --sim devp2p --sim.limit discv4 --client go-ethereum,nethermind
 
 The client list may contain any number of clients. You can select a specific client
 version by appending it to the client name with `_`, for example:

clients/openethereum/enode.sh

@@ -71,7 +71,7 @@ This section explains what happens during a simulation run.
 For a single run, the user provides the name of the simulator to run, and a set of client
 names to run against. For example:
 
-    ./hive --sim ethereum/sync --client go-ethereum,besu,openethereum
+    ./hive --sim ethereum/sync --client go-ethereum,besu,nethermind
 
 Hive first builds simulator and client images using docker. It expects a Dockerfile in the
 `./simulators/ethereum/sync` directory as well as a Dockerfile for each client (in

clients/openethereum/genesis.json

@@ -179,7 +179,7 @@ You can test this build by running `docker build .` in the simulator directory.
 
 Finally, go back to the root of the repository (`cd ../../..`) and run the simulation.
 
-    ./hive --sim my-simulation --client go-ethereum,openethereum
+    ./hive --sim my-simulation --client go-ethereum,besu
 
 You can check the results using [hiveview].
 

clients/openethereum/mapper.jq

@@ -57,10 +57,8 @@ mkdir $RESULTS
 # Sync are quick tests
 #
 
-# These three can succsessfully sync with themselves
-#testsync openethereum_latest
+# These can succsessfully sync with themselves
 #testsync go-ethereum_latest
-testsync openethereum_latest,go-ethereum_latest
 
 # These two are failing - even against themselves
 testsync besu_latest       # fails
@@ -69,7 +67,6 @@ testsync nethermind_latest # fails
 #testsync besu_latest,nethermind_latest
 
 #testsync go-ethereum_latest go-ethereum_stable
-#testsync go-ethereum_latest openethereum_latest
 #testsync go-ethereum_latest nethermind_latest
 #testsync go-ethereum_latest besu_latest
 
@@ -84,12 +81,10 @@ testgraphql besu_latest
 #testdevp2p go-ethereum_latest
 #testdevp2p nethermind_latest
 #testdevp2p besu_latest
-#testdevp2p openethereum_latest
 
 
 # These take an extremely long time to run
 #testconsensus go-ethereum_latest
-#testconsensus openethereum_latest
 #testconsensus nethermind_latest
 #testconsensus besu_latest