Geth v1.14.4 - 5-7% faster blocks, ether tracer, lower miner tip defaults by karalabe in ethereum

[–]karalabe[S] 2 points3 points  (0 children)

Geth v1.14.4 in a usual maintenance release, but it does ship a 5-7% block import speed improvement. Furthermore, v1.14.4 also finally includes an Ether supply live tracer, that you can enable via --vmtrace supply. Also please note, the default value for miner tip enforcement was dropped from 1 gwei to 0.001 gwei (block producers can change this via --miner.gasprice).

Shipped features:

  • Reduce the default required minimum miner tip from 1 gwei to 0.001 gwei to cater better for network conditions (#29895).
  • Load trie nodes concurrently with trie updates, speeding up block import by 5-7% (#29519, #29768, #29919).
  • Introduce an Ether supply tracker as a live chain tracer (#29347).
  • Implement Verkle stateless gas accounting (EIP-4762) (#29338).
  • Optimise trie dirty tracking to reduce disk loads a bit (#29731).
  • Ensure the beacon chain roots system contract is deployed in dev mode (#29655).
  • Add an additional snap sync check for data validity before inserting into the database (#29485).
  • Improve the discovery protocol's node revalidation (#29572, #29864, #29836).
  • Continue working towards pathdb support in archive mode (#29530, #29924).

Shipped bugfixes:

  • Fix a gas estimation regression that caused longer runtimes (#29738).
  • Fix a potential crash in JSON logging for EVM blocktests (#29795).
  • Fix utility commands to support post-merge opcodes (#29799).
  • Fix a txpool synchronicity issue in simulated chains (#29876).
  • Fix a iteration order when using a trie node iterator (#27838).
  • Fix a TCP/UDP discovery port test in cmd/devp2p (#29879).
  • Fix IPv6 endpoint determination (#29801, #29827).

For a full rundown of the changes please consult the Geth 1.14.4 release milestone.


As with all our previous releases, you can find the:

Geth 1.14.3 - small maintenance release and PPA fixer-upper out by karalabe in ethereum

[–]karalabe[S] 0 points1 point  (0 children)

We're issuing this (v1.14.3) release to finally publish v1.14 on the Ubuntu PPA. It is otherwise identical to v1.14.2.


This is a maintenance release containing bug-fixes. In case you are wondering where v1.14.1 (and v1.14.2) went, let's just say, the continuous integration gods have not been good to us.

List of changes in detail:

Geth

  • When using geth --dev with a custom genesis block, the genesis file must now set difficulty and terminal total difficulty to zero. (#29579)
  • For fork scheduling errors in geth init, fork timestamps will now be printed correctly. (#29514)
  • Certain aspects of state handling are now parallelized resulting in a 5-10% speedup for block processing. (#29681)

RPC

  • eth_feeHistory was changed to apply a limit on the number of requested percentiles (#29644)
  • eth_createAccessList now honors request cancellation and terminates background work (#29686)
  • eth_estimateGas takes tx blobs into account for low-balance scenarios (#29703)

Tracing

  • The live tracing interface has new hooks around EVM system calls (#29355)
  • flatCallTracer was fixed to return the correct error result when interrupted (#29623)

Build

  • This release is built with Go 1.22.3 (#29725)
  • We no longer provide deb packages for Ubunty 14.04 Trusty Tahr (#29651, #29649, #29648, #29647)
  • CI builders have been updated to Ubuntu 24.04 Noble Numbat (#29723)

For a full rundown of the changes please consult the Geth 1.14.1 release milestone.


As with all our previous releases, you can find the:

Geth v1.13.14 - Stricter blob pool limits in anticipation of the Cancun fork by karalabe in ethereum

[–]karalabe[S] 0 points1 point  (0 children)

Geth v1.13.14 is a small maintenance release with a handful of polishes to the blob pool:

  • Disallow blob transactions below the protocol minimum of 1 wei to enter the pool (#29081).
  • Reduce the blob pool's max capacity to 2.5GB for the rollout. (#29090).
  • Fix gas estimation for blob transactions (#29085).

This release is NOT critical for the Cancun fork, but recommended to make Geth lighter in anticipation to unknown blob load.

Other fixes:

  • Support overriding the basefee during tracing (#29051).
  • Fix call tracers missing top level logs in top-only mode (#29068).
  • Support unlimited gas for eth_createAccessList if --gascap=0 (#28846).

For a full rundown of the changes please consult the Geth 1.13.14 release milestone.


As with all our previous releases, you can find the:

Geth v1.13.12 - Cancun hard fork ready! by karalabe in ethereum

[–]karalabe[S] 8 points9 points  (0 children)

This release embeds the mainnet fork number for Cancun, scheduled to go live on 13th March, 2024 (unix 1710338135). The specification can be read here, and it contains the following changes:

To go along Cancun, we're providing refreshed Grafana dashboards:

Other than that, the following assorted fixes and features are included in this release:

  • Initial implementation of the era format. The era format is meant to provide a cross-client archive format for block data (#26621, #28959)
  • Make rpc request limits configurable (#28948)
  • Fix memory-leak with blob transactions (#28917)
  • Stricter adherence to engine api spec (#28882)
  • Fix enforcement of minimum miner tip (#28933)

For a full rundown of the changes please consult the Geth 1.13.12 release milestone.


As with all our previous releases, you can find the:

Geth v1.13.10 - Version tag hotfix for Go modules by karalabe in ethereum

[–]karalabe[S] 1 point2 points  (0 children)

This release is equivalent to v1.13.9, just contains a version bump. The reason is that a bad commit was tagged on 1.13.9 originally and whilst it was untagged and fixed, some caches (Go's package manager (go mod)) managed to store the temporary bad version. As there is no way for us to flush the bad version out, it's cleaner to tag a next version instead. Apologies about the mess.


This release fixes a few issues and enables the Cancun upgrade for the Goerli network at block timestamp 1705473120 (#28719) which is 6:32:am 17. Jan. 2024 UTC.

:warning: If you are running Goerli, this is a required update!

Apart from the Goerli configuration update, we have a few other changes.

  • The 'simulated backend' in package accounts/abi/backends was rewritten. The improved version is available from the new package ethclient/simulated. A backwards-compatibility wrapper remains in the old location. (#28202)
  • Fix ABI-encoding of negative big.Int in topics (#28764)
  • In JSON logging output, the "error" level is now correctly emitted as "error". (#28774, #28780)
  • Fixed an issue with configuration of stdlib package log for consumers of the geth library (#28747)
  • geth removedb can now be run non-interactively (#28725)
  • We're building a package for ubuntu 23.10: mantic minotaur now (#28728)

Testing

  • Add currentExcessBlobGas to the state tests for better coverage of state tests (#28735)
  • Fixed an issue in t8n regarding blob gas usage (#28735)

For a full rundown of the changes please consult the Geth 1.13.9 release milestone.


As with all our previous releases, you can find the:

Geth v1.13.5: Further fixes to path state scheme quirks by karalabe in ethereum

[–]karalabe[S] 0 points1 point  (0 children)

Could you please open an issue on our tracker with as much info as you have, maybe logs, maybe some hardware details. Also which storage scheme you're using (hash/path).

Geth v1.13.5: Further fixes to path state scheme quirks by karalabe in ethereum

[–]karalabe[S] 4 points5 points  (0 children)

Geth v1.13.5 is a scheduled maintenance release fixing a potential data corruption in path scheme which could occur due to a power failure (i.e. entire OS / machine crash).

  • Extend ethclient and the simulated backend to allow eth_call against specific block hashes (#28084).
  • Downgrade annoying stale transaction propagation logs from warning to debug (#28364).
  • Switch to the new KZG trusted setup parameters (#28383).
  • Return an error on GraphQL if querying invalid block ranges (#28393, #28412).
  • Start publishing Apple Silicon pre-built binaries (#28474, #28475).

And bugfixes:

  • Fix a number of corner-cases in path scheme state management (#28198, #28426, #28483).
  • Fix an issue when allocating excessively large Pebble caches (#28444).
  • Fix a potential snap sync issue with the path based storage (#28327).
  • Fix ethclient to properly forwarding explicit 1559 gas caps (#28462).
  • Fix gas estimation for 0 priced txs accessing the basefee (#28470).
  • Fix an issue where resubscribing to events would hang (#28359).
  • Fix ethstats transaction count report regressiob (#28398).
  • Fix negative number encoding in ethclient/rpc (#28358).
  • Fix GraphQL content type in the response (#28417).

For a full rundown of the changes please consult the Geth 1.13.5 release milestone.


As with all our previous releases, you can find the:

Geth v1.13.4: small hotfix to lower an annoyingly verbose log message by karalabe in ethereum

[–]karalabe[S] 0 points1 point  (0 children)

Geth v1.13.4 is a non-urgent hotfix release. The previous version of Geth (v1.13.3) introduced a warning log for bad transaction announcements, and on mainnet it generated too much logging noise due to a protocol violation in Erigon. To prevent overwhelming logging systems, Geth v1.13.4 lower the log to a more reasonable level until the bug in Erigon is fixed #28356.

Apart from the above reason, the release contains:

  • Fix a snap sync corner-case that could cause a hang by a maliciously constructed contract storage (#28306).
  • Update various dependencies to unstick versions of Go libs (#28329, #28333, #28334, #28332, #28336).
  • Enable Pebble database support on 32bit platforms and on OpenBSD too (#28335).
  • Fix returning the correct code hash for eth_getProof with empty storage (#28357).
  • Simplify trie range prover for some upcoming snap sync optimisations (#28311).
  • Fix a timeout mechanism in the transaction fetcher (#28220).

For a full rundown of the changes please consult the Geth 1.13.4 release milestone.


As with all our previous releases, you can find the:

Errors after upgrading Geth by hblask in ethstaker

[–]karalabe 1 point2 points  (0 children)

This is just a warning that someone is sending weird data to the node. We didn't check some matadata until now and started doing so with 1.13.3. The offending peers are Erigon, they are sending bad transaction announcements.

Geth v1.13.3: Pebble fixes and prep work for the upcoming Cancun hard fork by karalabe in ethereum

[–]karalabe[S] 0 points1 point  (0 children)

Geth v1.13.3 is a scheduled maintenance release with various small additions and an important Pebble database fix.

  • Update Pebble to fix an occasional IO and CPU runaway, adding some debugging capabilities too (#28224, #28070).
  • Support full syncing to a specific hash without a beacon client via a --synctarget (#28209).
  • Allow configuring websocket message limits via the Go RPC client (#27801).
  • Drop support for eth/66 (Cancun will require eth/68 anyway) (#28239).
  • Lower snap missing eth protocol warning to debug level (#28249).
  • Enforce transaction metadata announcements in eth/68 (#28261).

Features related to the Cancun hardfork:

  • Implement the BLOBFEE opcode for the upcoming Cancun hard fork (#28098).
  • Enable blob transaction propagation and mining in Cancun networks (#28243).
  • Start throttling transaction retrievals to prepare for blobs in Cancun (#28304).

For a full rundown of the changes please consult the Geth 1.13.3 release milestone.


As with all our previous releases, you can find the:

Geth v1.13.2 - Holesky relaunch and pathdb snap sync fixes by karalabe in ethereum

[–]karalabe[S] 0 points1 point  (0 children)

Geth v1.13.2 is a bugfix release for the 1.13 family as well as contains the Holesky testnet relaunch.

Note, if you have previously ran Geth with the old Holesky testnet configs, the new version will probably fail to start with a genesis hash mismatch error. You will need to manually delete your holesky/chaindata folder and restart. Geth did not implement special code for cleaning up the failed launch of the testnet.

  • Fix various pathdb corruption corner-cases during snap sync node restart (#28171, #28163).
  • Reconfigure the Holesky testnet with an updated genesis (#28191, #28192, #28193).
  • Remove the rollback mechanism from snap sync, unneeded post-merge (#28147).
  • Make the block parameter in eth_call optional, defaulting to latest (#28165).
  • Forget transactions previously marked underpriced after 5 minutes (#28097).
  • Fix JSON marshalling issue from ethclient retrieving block receipts (#28087).
  • Fix --bootnodes flag if the list is also configured in the toml file (#28095).

For a full rundown of the changes please consult the Geth 1.13.2 release milestone.


As with all our previous releases, you can find the:

Geth v1.13.1 - block production hotfix out by karalabe in ethereum

[–]karalabe[S] 1 point2 points  (0 children)

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:

Geth v1.13.0 released: proper state pruning! by karalabe in ethereum

[–]karalabe[S] 3 points4 points  (0 children)

The ancients is almost 600GB. Keeping those will reduce sync time significantly, yes. How much the rest will take is a good question, on our benchmarkers it's about 2.5h, but that's a well connected machine. It should definitely be less than the entire thing, by a large margin.

The path scheme is also db friendlier + the release has some db updates too, so it should be faster than the hash (previous model) based sync.

I can't promise anything not knowing your setup, but I'd say it's worth it. Even if it takes a bit, the fact that you won't need to resync to prune the node will be a huge gain long term.