Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bump ethereum/go-ethereum to v1.14.3 #94

Merged

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented May 9, 2024

Bumps upstream version

Copy link
Author

github-actions bot commented May 9, 2024

DAppNode bot has built and pinned the release to an IPFS node, for commit: ce2891f

This is a development version and should only be installed for testing purposes, install link

/ipfs/QmYF6rNEYax4RA77FiwxoKZQP1rSTdjFTtF9Vz9aryM5pS

(by dappnodebot/build-action)

@alexpeterson91 alexpeterson91 self-assigned this May 22, 2024
Copy link
Member

@alexpeterson91 alexpeterson91 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, been runnning on mainnet on multiple nodes since it came out 2 weeks ago. needed for all geth clients, and sets default state scheme to path needs a resync to change it but we can annouce that because it will work just fine with the current scheme used in most of our clients except holesky i think that was already set to path i think. but anyways this new release 1.14.x will default to path but not force a resync and will continue using hash if thats what the exissting data dir is, but we highly suggest that you wipe your volume anf resync on this version when convenient, no more pruning, no runaway state growth, cleaner shutdowns, and less dirty tries cached. current release we have for mainnet has a big security bug so this is kinda ASAP

@alexpeterson91 alexpeterson91 merged commit 7e8e5aa into master May 22, 2024
@alexpeterson91 alexpeterson91 deleted the dappnodebot/bump-upstream/ethereum/go-ethereum@v1.14.3 branch May 22, 2024 00:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant