# Core release v0.2.63

### Set-up

- [ ] Copy `/usr/src/dappnode/DNCORE/maindb.json` for future debugging
- [ ] Take notes about your selections of Ethereum and IPFS repository and staker pkgs selected
- [ ] Add Pablo ipfs peer /ipfs/Qma3Mef4r7RyqLAGbwVTaZtDAXvB94V12thMjkn2ihPhJt
- [ ] Install core v0.2.63 `/ipfs/Qma3Mef4r7RyqLAGbwVTaZtDAXvB94V12thMjkn2ihPhJt`
- [ ]

### Test

#### Critical test

- [ ] **Ethereum and IPFS repository**:
- [ ] Make sure the selections are the same as before the update at **system > advanced > repository**
- [ ] Switch from full node to remote and viceversa:
- [ ] Make sure the dappstore renders
- [ ] Check the Ethereum repository chain card is showing fine the status: "OK", "Using full node", "Using remote"...
- [ ] **Staker pkgs**:
- [ ] Make sure the selections are the same as before the update at **stakers > network**
- [ ] Make sure the pkgs selected still running
- [ ] Install pkg flow:
- [ ] Install Rotki from dappstore
- [ ] Stop Rotki
- [ ] Delete Rotki volumes
- [ ] Restart Rotki
- [ ] Delete rotki
- [ ] Future core update: install a "future" core update
- [ ] Auto-updates:

#### New features and fixes

- [ ] **Bug in full node using nimbus**: there is a bug in the full node for those users running Nimbus as Consensus client. The beacon API port in all the CCs is the 3500, but in Nimbus is the 4500 because is monoservice and the 3500 is already in used by the validator API.
- [ ] Select full node at **system > repository > Ethereum** with any Execution Client and Nimbus as Consensus client
- [ ] Once synced, make sure your Ethereum repository card in the dashboard says "Full node: Ok"
- [ ] **Full node - build beacon API dynamically**: Instead of hardcoding the ENS and the port of the beacon APIs from the consensus clients, use the chain driver from the manifest.
- [ ] Selelect full node at **system > repository > Ethereum** with ALL the combinations of EC and CC available.
- [ ] Make sure the status of the Ethereum repository card in the dashboard says the correct status: "syncing", "Full node: Ok"
- [ ] **If fallback activated, compare local execution latest block with remote**: When user is running full node with fallback activated, and the node is syncing there are some checks to trigger the fallback: execution syncing, consensus syncing, no errors, block distance between execution and consensus less than 1 day. From now on there is 1 more check that compares the latest block from the local Execution Client with the latest block of the remote Execution Client.
- [ ] (Hard to test) The fastest way to test this feature is to
- [ ] Add Nethermind trusted pubkey: there has been added Nethermind team pubkey for the `nethermind.dnp.dappnode.eth` and the `nethermind.public.dappnode.eth` so from now on the Nethermind team will release their own packages. This will ensure the Nethermind pkgs appear as signed for their signature:
- [ ] Check the trusted keys at **system > advanced > trusted keys**
- [ ] Add fee recipient to beacon service: Teku beacon service throws warnings if the fee recipient address is not set, looks like this is a good practice. From now on, every consensus client installed from the stakers UI, will attemp to set the fee recipient address in both services.
- [ ] Bug generating dynds keys: fixed by upgrading the nodejs version to LTS 19: upgrade nodejs version from 16 to 19.
- [ ] Delete the main db at **system > advanced > delete maindb**.
- [ ] Make sure you have no dynds keys at `cat /usr/src/dappnode/DNCORE/maindb.json`
- [ ] Restart dappmanager container
- [ ] Make sure the dynds keys has been regenerated at `cat /usr/src/dappnode/DNCORE/maindb.json`