Bump github.com/ethereum/go-ethereum from 1.12.2 to 1.13.1

[dependabot]

Bumps github.com/ethereum/go-ethereum from 1.12.2 to 1.13.1.

Release notes

Sourced from github.com/ethereum/go-ethereum's releases.

Zakros (v1.13.1)

Geth v1.13.1 is a hotfix release for v1.13.0.

It fixes the following issues:

• Fix the active fork detection on the engine API, causing the signer to create invalid blocks (#28135).
• Fix a db corruption in path scheme caused by a weirdly restarted snap sync (#28124, #28126).
• Fix geth db inspect command running against old hash scheme databases (#28108).
• Fix an effective gas price calculation regression on the RPC APIs (#28130).

Apart from the fixes, v1.13.1 introduces support for configuring Geth via environmental variables (#28103, #28119)!

For a full rundown of the changes please consult the Geth 1.13.1 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.

Therum (v1.13.0)

Geth v1.13.0 is a major milestone in the lifetime of Geth, bits and bobs being in development for around 6 years now. Since a release note cannot do it justice, please see our Geth v1.13.0 release blog post.

Still, just to quickly recap, Geth v1.13.0 finally ships a new database model which supports proper, full pruning of historical states; meaning you will never need to take your node offline again to resync or to manually prune. The new database model is optional for now (you need to enable it via --state.scheme=path) and does require resyncing the state, since we need to store it completely different (you can keep your ancients, no need to resync the chain too).

The path database will become the default eventually, but for safety reasons, we're keeping it opt-in for the moment. The old database model is not going away soon, though long term - unless there's something fundamentally wrong with the path db - it will. As for archive node users, we're working on a new model there too, but it does need a bit more work on top, so that's for another release.

The all important disclaimer: Geth's new path-based storage is considered stable and production ready, but was obviously not battle tested yet outside of the team. Everyone is welcome to use it, but if you have significant risks if your node crashes or goes out of consensus, you might want to wait a bit to see if anyone with a lower risk profile hits any issues.

---

Apart from the pruning work, the release contains:

• Built in support for the Holešky (Holešovice) testnet (#28007).
• Index transactions even if no blocks are received (#27847).
• Expose Geth version metadata into the metrics (#24877).
• Optimise eth_estimateGas to do fewer runs (#27710).
• Add eth_getBlockReceipts RPC API call (#27702).
• Support unpacking Solidity panic events (#27868).
• Reject GraphQL block queries where both number and hash is specified (#27876).
• Increase batch limits for RPC calls on the authenticated endpoint (#27924).
• Optimise logging library to avoid expensive call stack lookups (#28069).

And bugfixes:

• Fix forkid computation for genesis-merged non-zero timestamp networks (#27895, #28034).
• Fix a potential data race in the websocket ping/pong mechanism (#27733).

... (truncated)

Commits

• 3f40e65 params: release Geth v1.13.1
• c53b0fe core, eth/downloader: fix genesis state missing due to state sync (#28124)
• d8a351b params: fix typo in comment (#28129)
• 52234eb internal/flags: fix typo (#28133)
• 2177193 internal/ethapi: correctly calculate effective gas price (#28130)
• 9a9db3d eth/catalyst: fix engine API (#28135)
• 16cd1a7 cmd/geth, internal/flags: print envvar config source and bad names (#28119)
• 4fa3db4 eth/downloader: prevent pivot moves after state commit (#28126)
• 48fdb79 core/state: check err for iter.Error in fastDeleteStorage (#28122)
• 65a17c0 metrics: add support for enabling metrics from env vars (#28118)
• Additional commits viewable 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #98.