Bump the gomod-updates group with 3 updates

[dependabot]

Bumps the gomod-updates group with 3 updates: github.com/Masterminds/semver/v3, github.com/docker/docker and github.com/ethereum/go-ethereum.

Updates github.com/Masterminds/semver/v3 from 3.3.1 to 3.4.0

Release notes

Sourced from github.com/Masterminds/semver/v3's releases.

v3.4.0

There are a few changes in this release to highlight:

1. Constraints now has a property IncludePrerelease. When set to true the Check and Validate methods will include prereleases.
2. When an AND group has one constraint with a prerelease but more than one constraint then prereleases will be included. For example, >1.0.0-beta.1 < 2. In the past this would not have included prereleases because each constraint needed to have a prerelease. Now, only one constraint needs to have a prerelease. This is considered a long standing bug fix. Note, this does not carry across OR groups. For example, >1.0.0-beta.1 < 2 || > 3. In this case, prereleases will not be included when evaluating against >3.
3. NewVersion coercion with leading "0"'s is restored. This can be disabled by setting the package level property CoerceNewVersion to false.

What's Changed

• fix the CodeQL link by @​dmitris in Masterminds/semver#257
• Restore detailed errors when failed to parse with NewVersion by @​mattfarina in Masterminds/semver#262
• updating go version tested with by @​mattfarina in Masterminds/semver#263
• Restore the ability to have leading 0's with NewVersion by @​mattfarina in Masterminds/semver#266
• Handle pre-releases on all in an and group by @​mattfarina in Masterminds/semver#267
• Add property to include prereleases by @​mattfarina in Masterminds/semver#268
• Updating the error message handling by @​mattfarina in Masterminds/semver#269
• Update the release notes and readme for new version by @​mattfarina in Masterminds/semver#270

New Contributors

• @​dmitris made their first contribution in Masterminds/semver#257

Full Changelog: Masterminds/semver@v3.3.1...v3.4.0

Changelog

Sourced from github.com/Masterminds/semver/v3's changelog.

3.4.0 (2025-06-27)

Added

• #268: Added property to Constraints to include prereleases for Check and Validate

Changed

• #263: Updated Go testing for 1.24, 1.23, and 1.22
• #269: Updated the error message handling for message case and wrapping errors
• #266: Restore the ability to have leading 0's when parsing with NewVersion. Opt-out of this by setting CoerceNewVersion to false.

Fixed

• #257: Fixed the CodeQL link (thanks @​dmitris)
• #262: Restored detailed errors when failed to parse with NewVersion. Opt-out of this by setting DetailedNewVersionErrors to false for faster performance.
• #267: Handle pre-releases for an "and" group if one constraint includes them

Commits

• 61fc460 Merge pull request #270 from mattfarina/relnotes-3.4.0
• 69a63e7 Update the release notes and readme for new version
• dc05094 Merge pull request #269 from mattfarina/lowercase-error-strings
• a2cd9c2 Updating the error message handling
• 9760c47 Merge pull request #268 from mattfarina/include-prerelease
• c374751 Add property to include prereleases
• 057c901 Merge pull request #267 from mattfarina/fix-259
• abab1c2 Handle pre-releases on all in an and group
• ebda872 Merge pull request #266 from mattfarina/restore-calver
• 4ed619e Restore the ability to have leading 0's with NewVersion
• Additional commits viewable in compare view

Updates github.com/docker/docker from 28.2.2+incompatible to 28.3.0+incompatible

Release notes

Sourced from github.com/docker/docker's releases.

28.3.0

For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones:

• docker/cli, 28.3.0 milestone
• moby/moby, 28.3.0 milestone
• Deprecated and removed features, see Deprecated Features.
• Changes to the Engine API, see API version history.

New

• Add support for AMD GPUs in docker run --gpus. moby/moby#49952
• Use DOCKER_AUTH_CONFIG as a credential store. docker/cli#6008

Bug fixes and enhancements

• Ensure that the state of the container in the daemon database (used by /containers/json API) is up to date when the container is stopped using the /containers/{id}/stop API (before response of API). moby/moby#50136
• Fix docker image inspect inspect omitting empty fields. moby/moby#50135
• Fix docker images --tree not marking images as in-use when the containerd image store is disabled. docker/cli#6140
• Fix docker pull/push hang in non-interactive when authentication is required caused by prompting for login credentials. docker/cli#6141
• Fix a potential resource leak when a node leaves a Swarm. moby/moby#50115
• Fix a regression where a login prompt on docker pull would show Docker Hub-specific hints when logging in on other registries. docker/cli#6135
• Fix an issue where all new tasks in the Swarm could get stuck in the PENDING state forever after scaling up a service with placement preferences. moby/moby#50211
• Remove an undocumented, hidden, top-level docker remove command that was accidentally introduced in Docker 23.0. docker/cli#6144
• Validate registry-mirrors configuration as part of dockerd --validate and improve error messages for invalid mirrors. moby/moby#50240
• dockerd-rootless-setuptool.sh: Fix the script from silently returning with no error message when subuid/subgid system requirements are not satisfied. moby/moby#50059
• containerd image store: Fix docker push not creating a tag on the remote repository. moby/moby#50199
• containerd image store: Improve handling of errors returned by the token server during docker pull/push. moby/moby#50176

Packaging updates

• Allow customizing containerd service name for OpenRC. moby/moby#50156
• Update BuildKit to v0.23.1. moby/moby#50243
• Update Buildx to v0.25.0. docker/docker-ce-packaging#1217
• Update Compose to v2.37.2. docker/docker-ce-packaging#1219
• Update Docker Model CLI plugin to v0.1.30. docker/docker-ce-packaging#1218
• Update Go runtime to 1.24.4. docker/docker-ce-packaging#1213, moby/moby#50153, docker/cli#6124

Networking

• Revert Swarm related changes added in 28.2.x builds, due to a regression reported in moby/moby#50129. moby/moby#50169
  • Revert: Fix an issue where docker network inspect --verbose could sometimes crash the daemon (moby/moby#49937).
  • Revert: Fix an issue where the load-balancer IP address for an overlay network would not be released in certain cases if the Swarm was lacking an ingress network (moby/moby#49948).
  • Revert: Improve the reliability of NetworkDB in busy clusters and lossy networks (moby/moby#49932).
  • Revert: Improvements to the reliability and convergence speed of NetworkDB (moby/moby#49939).
• Fix an issue that could cause container startup to fail, or lead to failed UDP port mappings, when some container ports are mapped to 0.0.0.0 and others are mapped to specific host addresses. moby/moby#50054
• The network inspect response for an overlay network now reports that EnableIPv4 is true. moby/moby#50147
• Windows: Improve daemon startup time in cases where the host has networks of type "Mirrored". moby/moby#50155
• Windows: Make sure docker system prune and docker network prune only remove networks created by Docker. moby/moby#50154

... (truncated)

Commits

• 265f709 Merge pull request #50247 from vvoland/50245-28.x
• b2a9318 docs: cut api docs for v1.51
• b3e2e22 Merge pull request #50244 from vvoland/50177-28.x
• c571cd8 Merge pull request #50243 from vvoland/50238-28.x
• 8c713c1 gha: lower timeouts on "build" and "merge" steps
• 539c115 Merge pull request #50240 from thaJeztah/28.x_backport_validate_mirrors
• 8e7ea47 vendor: update buildkit to v0.23.1
• 222baf4 vendor: github.com/moby/buildkit v0.23.0
• 1627e82 Merge pull request #50241 from thaJeztah/28.x_backport_update_cgroups
• 4070ebd Merge pull request #50242 from thaJeztah/28.x_backport_fix_event_ordering
• Additional commits viewable in compare view

Updates github.com/ethereum/go-ethereum from 1.15.1 to 1.16.0

Release notes

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

Terran Rivets (v1.16.0)

We are proud to present the v1.16.0 release, introducing path-based archive node and several other improvements to the state database implementation. There is also the usual amount of bug fixes and small improvements.

Archive Node

This release includes a new, experimental implementation of the archive node (--gcmode=archive). As an archive node, Geth stores all historical states, and can thus retrieve account balances, nonces and storage values at old blocks.

In previous versions of Geth, running as an archive node was only possible using the legacy 'hash-based' state storage scheme (--state.scheme=hash). When syncing mainnet the resulting database would reach sizes larger than 20TB, and it all had to be stored on a high-speed SSD.

The new implementation provides the state archive in combination with 'path-based' storage (--state.scheme=path). Comparing to hash-based storage, there are three basic advantages:

• Geth can be configured to store historical states on a dedicated disk, and it doesn't have to be an SSD (it will be ~3x faster to access when stored on SSD though).
• For the full state history of mainnet, the state database will have a size of ~1.9TB (this is without the tx-by-hash index and log index).
• The amount of historical state kept by the node is configurable as well. By default, Geth will keep historical state for the last 90k blocks, and older state is pruned from disk automatically as the chain advances. You can set the number of states to keep with the --history.state flag.

Notably, there is also one drawback with the new archive node: eth_getProof is not supported for historical blocks. With --state.scheme=path, Geth can only serve state proofs for the latest 128 blocks. We believe this is an acceptable tradeoff. If you need older proofs, you can still a hash-based archive node as before, but we'd also really like to hear about your use case. Please contact us via email at [email protected] so we can learn more, and possibly find a solution that can be implemented within Geth.

How it works

With 'path-based' state storage, Geth keeps exactly one full state in the database. Specifically, the persistent state is 128 blocks in the past. For newer blocks up to the head, forward diffs are kept in memory. In order to support rolling back to blocks older than head-128, Geth also keeps 'state history' in the form of reverse key-value diffs. When the chain is reset to an old block, these diffs are applied to the persistent state, going backwards one diff at a time until the target block is reached.

A reverse state diff contains the previous values of all modified accounts and storage locations for a specific block. There is a reverse diff for each historical block. This makes reverse diffs suitable for storage into the 'freezer', i.e. they do not need to live within Pebble/LevelDB.

The new archive mode is built on the realization that reverse state diffs contain all necessary data to serve historical state queries. For example, in order to get the historical balance of an account X at block B, we can search forward through diffs starting at block B until we find a block where account X is modified. This diff will contain the balance of the account, since it stores the all modified pre-values.

To accelerate the search for a suitable diff, Geth creates a database index storing the block numbers in which an account was modified. This index is small compared to the overall state history, but it is crucial for correct operation of the archive node. The state index is stored in PebbleDB and will be generated automatically while geth is syncing the chain. It takes ~30h to build the archive state index for mainnet, and historical state will only be available when the index is fully built. Geth will report a syncing status through eth_syncing while the indexing happens.

Other state implementation changes

In v1.16.0, the implementation of the 'state snapshot' has been rewritten for improved integration with path-based state storage. As you may recall, Geth stores the state in two different ways:

• The 'snapshot' contains the flat keys and values of the state, in a layer-based struture.
• The trie database contains state trie nodes, necessary for the state root computation.

When the implementation of the snapshot and its layer tree was introduced in Geth v1.10.0, it was built to be entirely separate from the trie database. We added path-based state storage in v1.13.0, and that system contains a layer tree as well, with slight differences in semantics and implementation.

As of this release, the layer trees of the state snapshot and trie database have been merged into a single implementation (#30661). In path-based mode, the trie database now holds a reference to the corresponding snapshot layer for each tree state. The new layer tree has also been enhanced with an additional index of layers in which an account was modified (#30971). Note this is similar in spirit to the historical state index. The new index will enable us to increase the number of in-memory state layers in the future.

Full list of changes in this release

Geth

• The default block gas limit is now 45M. (#32087)
• Geth can now use era1 files to access history when running with pruned history. (#31604)
• There is a new geth download-era subcommand for fetching era1 files. (#31823, #31951, #32081)
• When Geth is interrupted while it is syncing, pending block imports will now be canceled, leading to a quicker shutdown. (#32062)
• Ready for fork activation messages are now printed based on the current clock time. (#31800)
• Geth no longer allows setting a different network ID when running a network preset. (#31630)

... (truncated)

Commits

• 57f8971 version: release go-ethereum v1.16.0 stable
• 0c90e4b all: incorporate state history indexing status into eth_syncing response (#32...
• 36bcc24 triedb/pathdb: fix journal resolution in pathdb (#32097)
• a92f2b8 core, eth, triedb: serve historical states over RPC (#31161)
• ce63bba eth, triedb/pathdb: permit write buffer allowance in PBSS archive mode (#32091)
• 429e821 cmd/utils: fix formatting for beacon flag errors to fit Fatalf form (#32090)
• cafa5e6 core, consensus/beacon: defer trie resolution (#31725)
• 6dd38d2 cmd/geth, triedb: add pathdb state verification (#32086)
• 9c5c0e3 core/rawdb, triedb/pathdb: implement history indexer (#31156)
• ebff350 miner: default gaslimit 45M (#32087)
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• Queue - adds this PR to the back of the merge queue
• Hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[macroscopeapp]

Update Go module dependencies including ethereum/go-ethereum from v1.15.1 to v1.16.1 and switch KZG cryptography implementations from go-kzg-4844 to go-eth-kzg

Updates multiple Go module dependencies in go.mod with the most significant changes being:

• Upgrades github.com/ethereum/go-ethereum from v1.15.1 to v1.16.1
• Switches KZG cryptography implementations by removing github.com/crate-crypto/go-kzg-4844 v1.1.0 and adding github.com/crate-crypto/go-eth-kzg v1.3.0
• Updates github.com/ethereum/c-kzg-4844 to v2.1.0 with new import path
• Updates github.com/consensys/gnark-crypto from v0.14.0 to v0.18.0
• Updates github.com/docker/docker from v28.2.2+incompatible to v28.3.0+incompatible
• Updates import paths in mock files from github.com/ethereum/go-ethereum/accounts/abi/bind to github.com/ethereum/go-ethereum/accounts/abi/bind/v2 in pkg/mocks/fees/mock_RatesContract.go and pkg/mocks/registry/mock_NodeRegistryContract.go

📍Where to Start

Start with the dependency changes in go.mod to understand the scope of the updates, then review the import path changes in the mock files.

---

Macroscope summarized b721c0e.

[mkysel]

it seems that geth is having some compatibility issues?

[fbac]

it seems that geth is having some compatibility issues?

It seems ethereum/go-ethereum#31887 (part of 1.16 release) introduced returning BlockTimestamp as part of logs, but it was returning not properly hex-encoded which made the marshal in CallContext fail, that's why our client.TransactionReceipt call was failing in the end.
They fixed it in 1.16.1, so I'm bumping it.