## Simulacrum ### Hashes Mi peer http://my.dappnode/#/system/add-ipfs-peer/%2Fdns4%2Ff6e36f19e349b0dd.dyndns.dappnode.io%2Ftcp%2F4001%2Fipfs%2F12D3KooWE9YGh2MojWYhLDaBhhxG7NH4ZNY5fS2TPXkqfvshP1cq **goerli** `/ipfs/QmPaLkGg7M3HSy3CwihqDeSiC2ro9TDiihXCoDAiMGTMvt` **prysm-prater** `/ipfs/QmZ3XbBMkkVVwgWobEmj3XG7KDPdD6g92cakT7taVPrXwG` **lighthouse-prater** `/ipfs/Qmbu2M9JY1pEpBbzXbAYAYTFiQzUb9tYHbmHMTfcqER6qA` **teku-prater** `/ipfs/Qmbja9JLNePfR4aL38vp7GWXXwD1J3xcEcPPwZ3GFEJfeY` **nimbus-prater** `/ipfs/QmYb2nZ47VTyuqTq5iqtPL9KBvWwdp7KSWSqgdomyiaxA3` **web3signer-prater** `/ipfs/QmWupLqFK2BXFm33d27UYBp4mPe2rFx2X6koZZkDtxE4gi` **dappmanager** `/ipfs/QmPyxsavrFk68rWw1ajFrpYquag2geg24HE1jjJwHfykb3` ### Initial state Have installed: - Latest core - Latest Prysm-prater - Latest web3signer-prater with Prysm option selected - Latest goerli-geth Have at least 1 prater validator ### Test 1. Update dappmanger (use hash). - Expected result: the db must reflect the corresponding configuration: ``` cat /usr/src/dappnode/DNCORE/maindb.json .... "mevboost-prater": false, "execution-client-prater": "goerli-geth.dnp.dappnode.eth", "consensus-client-prater": "prysm-prater.dnp.dappnode.eth" ``` - Check the stakers UI at **prater** and ensure the options of the clients are selected 2. Update Prysm-prater, web3signer-prater and goerli-geth (use hashes) - Expected result: - Validator still validates - Communication between EC and CC works fine (check logs) - Web3signer listen requests from the EC (check logs) - Ensure the global envs are setted propertly inside the EC, CC and WEB3SIGNER containers executing `env` command inside them 3. Remove Prysm-prater or goerli-geth or web3signer-prater - Expected result: the option must have been de-selected from the stakers UI 4. Reinstall the package removed on the previous step with the hash 5. Switch from Prysm to any other client - Expected result: the new CC must have been updated in the stakers UI. Check the `CONSENSUS_CLIENT_PRATER` ENV value has been updated in the EC (goerli-geth). - Because its not published yet, the previous step has installed the latest CC and web3signer, so update them through the above hashes. Ensure the communication works again