Home

Keeping this fork up to date

It's important for us to stay pretty close with the ethereum/go-ethereum releases in order for our nodes to be kept in sync. Occasionally there will be a hard fork where we must update to a certain release on a certain date. Examples from the past include the London and Berlin hard forks.

Steps to update

At the time of writing, we have a branch called statediff-develop which is based on the tagged release (v1.10.12-vdb-go-ethereum) in this repo (commit da8aef1c7). In order to do an upgrade we will be checking out a branch from statediff-develop, merging upstream geth changes, resolving conflicts, running geth repo tests, running an integration test, and opening/merging a PR.

1. From the statediff-develop branch git checkout upgrade/v1.10.x
2. Make sure you have a remote setup that points to the upstream github.com:ethereum/go-ethereum repo [include add remote steps]
3. git fetch upstream --tags
4. git merge v1.10.x
5. Resolve any conflicts that may have occurred
6. Run the tests in the repo make test
7. Open a PR from upgrade/v1.10.x to statediff-develop and merge
8. Tag the release v1.10.x-vdb-go-ethereum

Deploying the new version of the node

We'll need to build the image, tag it, and push to dockerhub so its available in AWS.

1. From your local tagged release branch, build an image and tag it for dockerhub docker build . -t makerdao/vdb-go-ethereum:v1.10.x
2. Push the new image to docker docker push makerdao/vdb-go-ethereum:v1.10.x