ChainWalker
                                
                                
                                
                                    ChainWalker copied to clipboard
                            
                            
                            
                        Bump github.com/ethereum/go-ethereum from 1.10.22 to 1.10.23
Bumps github.com/ethereum/go-ethereum from 1.10.22 to 1.10.23.
Release notes
Sourced from github.com/ethereum/go-ethereum's releases.
Sentry Omega (v1.10.23)
Geth v1.10.23 is a hotfix release for a pruning regression that was introduced in v1.10.22. For technical details on the bug, please check out the PR that fixes it.
If anyone updated to v1.10.22 in these past couple of days, there is a fairly high probability that some state data might have gone missing from your node. Doing a full check on the state is possible
geth snapshot traverse-state, but will likely take a day and the fix is all the same anyway.To ensure that your node has all the data, please rewind your local chain to a block before you updated (if unsure, just pick a block before the release time) with
debug.setHead("0xblock-number-in-hex")via the Geth console (on IPC), ordebug_setHeadvia JSON RPC (you might need to temporarilly expose thedebugnamespace to do that). The brute force alternative of course is to resync after an update, which you can do by deleting yourchaindatafolder (but please leave theancientfolder within to keep the blocks).We apologize for this regression and the headaches fixing it will entail on your side. We've learnt the hard way that there's an untested class of bugs that appear across full sync restarts.
For a full rundown of the changes please consult the Geth 1.10.23 release milestone.
As with all our previous releases, you can find the:
- Pre-built binaries for all platforms on our downloads page.
 - Docker images published under
 ethereum/client-go.- Ubuntu packages in our Launchpad PPA repository.
 - OSX packages in our Homebrew Tap repository.
 
Original Merge release notes
Geth
v1.10.22v1.10.23 enables the Merge for the Ethereum mainnet at a Terminal Total Difficulty of58_750_000_000_000_000_000_000.This TTD is expected to be reached on the 15. September 2022.
Merge EIPs
Additional notes about the merge changes
- This release configures the Terminal Total Difficulty for mainnet. (#25528)
 - Many engine API issues found by hive have been fixed for this release. (#25552, #25423, #25414, #25416, #25428)
 - The Goerli testnet is now internally configured as 'successfully merged'. (#25519, #24538)
 JSON-RPC API
- The log filtering system now uses a LRU cache for block logs, speeding up repeated queries for the same block range. The cache size can be configured using the
 --cache.blocklogscommand-line flag. (#25459)eth_createAccessListis now much faster when no gas limit is provided. (#25467)eth_feeHistorynow also works with thefinalizedblock specifier. (#25442)- The built-in callTracer now supports an option
 onlyTopCall. Enabling this option makes the tracer skip internal calls. We added this option to enable use of thecallTracerto get the return data of reverted transactions. (#25430)Go-library changes
- Storage of trie node hash preimages is now disabled by default. You can enable it again using the
 --cache.preimagesflag. (#25287, #25538, #25533)- The ethash mining implemenation now removes temporary DAG files, which could be left of disk when geth was interrupted while generating a DAG. (#25381)
 - ethclient now supports the
 eth_feeHistorymethod. (#25403)
... (truncated)
Commits
d901d85params: release Geth v1.10.234c114afMerge pull request #25582 from holiman/err_handling9ed10b9Merge pull request #25581 from karalabe/triedb-fix-flush-order45a660aconsensus/beacon: don't ignore errors5758d1fcore/state, trie: fix trie flush order for proper pruning81bd998core, eth/downloader: handle spurious junk bodies from racey rollbacks (#25578)6d711f0params: begin v1.10.23 release cycle- See full diff in compare view
 
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)