Commit 6b5839d
authored
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4&size=40){kind=avatar}
chore: Bump github.com/ethereum/go-ethereum from 1.13.14 to 1.14.0 (#305)
Bumps
[github.com/ethereum/go-ethereum](https://github.com/ethereum/go-ethereum)
from 1.13.14 to 1.14.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/ethereum/go-ethereum/releases">github.com/ethereum/go-ethereum's
releases</a>.</em></p>
<blockquote>
<h2>Asteria (v1.14.0)</h2>
<p>Geth v1.14.0 (Asteria) is a major release with some juicy new
features as well as some breaking changes. Please read through the
release notes before updating to it. Whilst it should not adversely
impact most users, there're always those rare occurrences.</p>
<h3>Highlights</h3>
<ul>
<li>
<p>Geth v1.14.0 switches over the default state trie representation from
<code>hash</code> mode to <code>path</code> mode (i.e.
<code>--state.scheme</code> flipped form <code>hash</code> to
<code>path</code>) (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29108">#29108</a>).
This change does not affect Geth instances with pre-existing databases,
in the case of which Geth continues to use whatever the existing
database's format is. If no previous database exists however, for full
nodes, Geth will now default to <code>pathdb</code>. The main advantage
is built-in, online historical state pruning; no more runaway state
growth.</p>
<ul>
<li><strong>If you want to force the old behaviour, you can run Geth
with <code>--state.scheme=hash</code> for now.</strong> That said, we
will be dropping <code>hash</code> mode sooner rather than later, so we
advise everyone running full nodes to gradually switch, if they haven't
yet.</li>
<li><strong>Archive mode support is not yet finalised for
<code>path</code> mode, so archive nodes will still run in
<code>hash</code> mode.</strong> Naturally, hash mode will not be
dropped until a full <code>path</code> archive lands and people have
enough time to switch to it.</li>
</ul>
</li>
<li>
<p>Geth v1.14.0 introduces a brand new <em>live-tracing</em> feature,
where one or more transaction tracers might be injected into the block
processing pipeline, ensuring that tracing and execution happen in
lockstep (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29189">#29189</a>).
Since Go does not have a cross platform, OS native plugin
infrastructure, adding live tracers needs to be done at the Geth source
code level, and Geth itself subsequently rebuilt. That said, the
advantage is that such tracers have full execution flexibility to do
whatever they like and however they like. Please see the live-tracer <a
href="https://github.com/ethereum/go-ethereum/blob/master/core/tracing/CHANGELOG.md">changelog</a>
and <a
href="https://geth.ethereum.org/docs/developers/evm-tracing/live-tracing">docs</a>
for details.</p>
<ul>
<li><strong>Live tracing runs in lockstep with block execution, one
waiting for the other.</strong> You should never run a live tracer on a
validating node, or any other where latency is important. The
recommended practice is to have tracers collect and export the bare
minimum data needed and do any post-processing in external systems where
latency is not relevant.</li>
<li><strong>The live tracer work required a number of breaking internal
API changes.</strong> If you had your own native tracers implemented
before this change, the <a
href="https://github.com/ethereum/go-ethereum/blob/master/core/tracing/CHANGELOG.md">changelog</a>
contains the necessary steps needed to update your old code for the new
APIs.</li>
</ul>
</li>
<li>
<p>Geth v1.14.0 replaces the completely random transaction propagation
paths (in the Ethereum P2P network) with pseudo-random ones, that ensure
transactions from the same account follow the same path in the network
(as long as no peer churn happens). The purpose is to allow a burst of
transactions from the same account to ripple through the network on the
same connections, minimising reordering. Whilst this doesn't provide any
guarantees, nor does it replace the potential need for more complex
routing logic, it should make nonce gaps significantly less likely,
reducing the probability of dropped transactions during bursts (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29034">#29034</a>).</p>
<ul>
<li><strong>This change only applies to networking, so other clients are
not required to follow suit.</strong> That said, the network would
behave more consistently overall if all clients implemented some similar
logic (the exact routing algorithm is irrelevant, as long as it's stable
in the accounts).</li>
</ul>
</li>
<li>
<p>Geth v1.14.0 drops support for running pre-merge networks (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29169">#29169</a>).
This does not mean that Geth will not be able to process or validate
pre-merge blocks, rather that starting v1.14.0, Geth <em>must</em> have
a consensus client drive it's chain selection. Geth drops the
<em>forward-sync</em> mode of operation, where it imports blocks based
on PoW (ethash) or PoA (clique) difficulties.</p>
<ul>
<li><strong>Non-merged networks will need to stick to Geth v1.13.x until
they transition to post-merge.</strong> As Ethereum has transitioned
towards a post-merge world, we cannot maintain a significant chunk of
code that's been dead for 2 years now on mainnet.</li>
<li><strong>Post-merge networks must be marked so with the
<code>terminalTotalDifficultyPassed: true</code> field in their
<code>genesis.json</code>.</strong> This requirement will be dropped
(along with even caring at all about this field) in a few releases, but
for now this field produces a clear error message for the user of what's
wrong with their pre-merge network.</li>
</ul>
</li>
<li>
<p>Geth v1.14.0 stops automatically constructing the pending block (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/28623">#28623</a>).
Performance wise there is a significant cost to creating a potential
pending block, yet most node operators do not care about it. Not even
validators need the pending block. This work also drops support for
mining/signing a block "off-demand" (i.e. not via the engine
API, rather by Geth itself), meaning Clique signing is also removed
going forward.</p>
<ul>
<li><strong>With Clique mining removed, Geth v1.14.0 cannot be a Clique
signer any more.</strong> This however goes hand-in-hand with the
removal or pre-merge chain selection and synchronisation support
described earlier.</li>
<li><strong>The pending block can still be constructed on demand for
now.</strong> Whenever an RPC method is called that is based on the
pending block, Geth will generate it on the fly and cache it for 1
second for subsequent calls. The first such call will have a few hundred
ms execution delay.</li>
</ul>
</li>
<li>
<p><strong>Geth v1.14.0 removes support for filtering pending
logs.</strong> This is following the previous change of creating the
pending block only on demand. We see next to no value in monitoring the
logs of a random subset of transactions that might (but probably mostly
will not) end up in the next block. Power users who wish to monitor the
transaction pool for MEV (or similar) purposes, should hook into Geth
directly and extract the exact data they need, rather than rely on
insufficient API endpoints.</p>
</li>
<li>
<p>Geth v1.14.0 ships a <em>beacon chain</em> light client (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/28822">#28822</a>,
<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29308">#29308</a>,
<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29335">#29335</a>,
<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29532">#29532</a>,
<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29567">#29567</a>).
It uses the REST API of beacon nodes and requires the <code>beacon /
light_client namespace</code>, currently supported by Lodestar and
Nimbus (<a
href="https://ethereum.github.io/beacon-APIs/#/Beacon">specs</a>).</p>
<ul>
<li><strong>The beacon light client provides access to consensus layer
data, not execution layer data.</strong> This currently means that it
can follow the beacon chain as a light client and extract the latest
head and finalised execution layer block. That can be used to drive a
full execution node without running an own beacon node. There is no
support yet for a full execution light client.</li>
<li><strong>Validation and staking is not possible with a beacon light
client.</strong> Since the sync committee signatures on each beacon head
are canonised in the next block, the beacon light client can only follow
the chain with one slot delay.</li>
<li><strong>The beacon light client exists both as a standalone
executable and integrated into Geth.</strong> The <code>blsync</code>
executable can drive any execution layer node through the standard
engine API or can just do a "test run" printing block numbers
and hashes to the console. The integrated mode can do the same inside
Geth. If you specify at least one suitable consensus layer REST API
endpoint with the <code>--beacon.api</code> flag, then Geth will run
without a beacon node connected through the engine API.</li>
</ul>
</li>
<li>
<p>Geth v1.14.0 switched to using Go v1.22 by default (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/28946">#28946</a>),
which means we've dropped support for Go v1.20. Geth also started using
of new features from Go v1.21 in our codebase, so building with Go v1.20
will probably error from now on. Just a heads up.</p>
</li>
</ul>
<h3>Features</h3>
<ul>
<li>Add the <code>geth db inspect-history</code> command to inspect
pathdb state history (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29267">#29267</a>).</li>
<li>Enable the Cancun hard-fork when running Geth in dev mode (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/28829">#28829</a>).</li>
<li>Use beacon chain finality as the marker to move old blocks into
ancients (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/28683">#28683</a>).</li>
<li>Drop large-contract (500MB+) deletion DoS protection from pathdb
post Cancun (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/28940">#28940</a>).</li>
<li>Switch Geth's USB library from <code>libusb</code> to
<code>hid</code> for simpler hardware wallet support (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/28945">#28945</a>,
<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29175">#29175</a>,
<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29176">#29176</a>).</li>
<li>Update the <code>prestateTrancer</code> to take into account 4844
blobs and their fees (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29168">#29168</a>).</li>
<li>Extend the <code>ethclient</code> and <code>gethclient</code>
packages with support for 4844 blob fields (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29198">#29198</a>).</li>
<li>Detailed block execution metrics are now always reported,
deprecating <code>--metrics.expensive</code> (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29191">#29191</a>).</li>
<li>Avoid a lot of memory allocations while shuffling 4844 blobs within
Geth (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29050">#29050</a>).</li>
<li>Switch to using Go's native <code>log/slog</code> package instead of
<code>golang/exp</code> (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29302">#29302</a>).</li>
<li>When computing state roots, apply state updates before deletes to
avoid some trie lookups. (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29201">#29201</a>).</li>
<li>Track not only total peer count, but also how many are inbound or
outbound (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29424">#29424</a>).</li>
<li>Add support for signing blob transactions (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/28976">#28976</a>,
<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29470">#29470</a>).</li>
<li>Surface <em>max initcode exceeded</em> errors from the VM to outer
callers (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/29354">#29354</a>).</li>
<li>Update the EVM to reject contract creation on top of non-empty
storage (<a
href="https://redirect.github.com/ethereum/go-ethereum/pull/28912">#28912</a>).</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/ethereum/go-ethereum/commit/87246f3cbaf10f83f56bc4d45f0f3e36e83e71e9"><code>87246f3</code></a>
params: release Geth v1.14.0</li>
<li><a
href="https://github.com/ethereum/go-ethereum/commit/5f3c58f1de9ef91dd22b632e6bcb559081d56e1d"><code>5f3c58f</code></a>
eth/downloader: fix case where skeleton reorgs below the filled block
(<a
href="https://redirect.github.com/ethereum/go-ethereum/issues/29358">#29358</a>)</li>
<li><a
href="https://github.com/ethereum/go-ethereum/commit/ade7515c812e96467dce51da39af346aa27df575"><code>ade7515</code></a>
eth, eth/tracers: process beacon root before transactions (<a
href="https://redirect.github.com/ethereum/go-ethereum/issues/29402">#29402</a>)</li>
<li><a
href="https://github.com/ethereum/go-ethereum/commit/fb08fd334a48e2ad07e0d5205c23368ec9cd2bec"><code>fb08fd3</code></a>
core/tracing: Add OnClose Trace Hook (<a
href="https://redirect.github.com/ethereum/go-ethereum/issues/29629">#29629</a>)</li>
<li><a
href="https://github.com/ethereum/go-ethereum/commit/882d1e22f66521d62ecdfe4566fb419765d744cf"><code>882d1e2</code></a>
cmd/geth, cmd/utils: rename config and flag to<code>
VMTraceJsonConfig</code> (<a
href="https://redirect.github.com/ethereum/go-ethereum/issues/29573">#29573</a>)</li>
<li><a
href="https://github.com/ethereum/go-ethereum/commit/94579932b18931115f28aa7f87f02450bda084c9"><code>9457993</code></a>
core/vm: fix Prague contracts (<a
href="https://redirect.github.com/ethereum/go-ethereum/issues/29612">#29612</a>)</li>
<li><a
href="https://github.com/ethereum/go-ethereum/commit/256d4b099cf540ba99181d6e746d4a1eaebef054"><code>256d4b0</code></a>
beacon/light: request finality update explicitly when necessary (<a
href="https://redirect.github.com/ethereum/go-ethereum/issues/29567">#29567</a>)</li>
<li><a
href="https://github.com/ethereum/go-ethereum/commit/b2b0e1da8cac279bf0466885d1abdc5d93402f41"><code>b2b0e1d</code></a>
all: fix various typos (<a
href="https://redirect.github.com/ethereum/go-ethereum/issues/29600">#29600</a>)</li>
<li><a
href="https://github.com/ethereum/go-ethereum/commit/709e0b399712f113a907936b9f73da8c33afd3f1"><code>709e0b3</code></a>
metrics: remove librato (<a
href="https://redirect.github.com/ethereum/go-ethereum/issues/29624">#29624</a>)</li>
<li><a
href="https://github.com/ethereum/go-ethereum/commit/0e380ddaf7d9ccba87d3a3688a3fb419b562451c"><code>0e380dd</code></a>
miner: fix typos (<a
href="https://redirect.github.com/ethereum/go-ethereum/issues/29625">#29625</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/ethereum/go-ethereum/compare/v1.13.14...v1.14.0">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
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)
</details>
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>1 parent 236d665 commit 6b5839d
2 files changed
+40
-41
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2 | 2 | | |
3 | 3 | | |
4 | 4 | | |
5 | | - | |
| 5 | + | |
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
| |||
11 | 11 | | |
12 | 12 | | |
13 | 13 | | |
14 | | - | |
| 14 | + | |
15 | 15 | | |
16 | 16 | | |
17 | | - | |
| 17 | + | |
18 | 18 | | |
19 | 19 | | |
20 | 20 | | |
| |||
25 | 25 | | |
26 | 26 | | |
27 | 27 | | |
28 | | - | |
29 | | - | |
30 | | - | |
31 | | - | |
32 | | - | |
33 | | - | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
34 | 33 | | |
35 | 34 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
18 | 18 | | |
19 | 19 | | |
20 | 20 | | |
21 | | - | |
22 | | - | |
23 | | - | |
24 | | - | |
25 | | - | |
26 | | - | |
27 | | - | |
28 | | - | |
29 | | - | |
30 | | - | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
31 | 29 | | |
32 | 30 | | |
33 | 31 | | |
| |||
38 | 36 | | |
39 | 37 | | |
40 | 38 | | |
41 | | - | |
42 | | - | |
| 39 | + | |
| 40 | + | |
43 | 41 | | |
44 | 42 | | |
45 | 43 | | |
| |||
48 | 46 | | |
49 | 47 | | |
50 | 48 | | |
51 | | - | |
52 | | - | |
53 | | - | |
54 | | - | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
55 | 53 | | |
56 | 54 | | |
57 | 55 | | |
| |||
60 | 58 | | |
61 | 59 | | |
62 | 60 | | |
| 61 | + | |
| 62 | + | |
63 | 63 | | |
64 | 64 | | |
65 | 65 | | |
| |||
69 | 69 | | |
70 | 70 | | |
71 | 71 | | |
72 | | - | |
73 | | - | |
| 72 | + | |
| 73 | + | |
74 | 74 | | |
75 | 75 | | |
76 | 76 | | |
| |||
159 | 159 | | |
160 | 160 | | |
161 | 161 | | |
162 | | - | |
163 | | - | |
| 162 | + | |
| 163 | + | |
164 | 164 | | |
165 | 165 | | |
166 | | - | |
167 | | - | |
168 | | - | |
169 | | - | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
170 | 170 | | |
171 | 171 | | |
172 | 172 | | |
173 | 173 | | |
174 | 174 | | |
175 | | - | |
176 | | - | |
| 175 | + | |
| 176 | + | |
177 | 177 | | |
178 | 178 | | |
179 | | - | |
180 | | - | |
181 | | - | |
182 | | - | |
183 | | - | |
184 | | - | |
| 179 | + | |
| 180 | + | |
| 181 | + | |
| 182 | + | |
| 183 | + | |
| 184 | + | |
185 | 185 | | |
186 | 186 | | |
187 | 187 | | |
| |||
0 commit comments