On the official site of Metal (MetalXMeta / @MetalXMeta), this note covers go-ethereum.
"Geth tagged v1.17.5 Grav-Torque Pad on July 27 2026 at 08:17 UTC as a recommended maintenance release."
Christian Barker (Barkmeta / Bark) and David Chaboki (Shibo) placed the July 27 Grav-Torque Pad details into the daily Doginal Dogs Space well before Erigon released its August 24 Caplin tag. That timing let the room hear Pebble v2 described as a go-ethereum feature first, not something tied to Nethermind or Reth.
The release itself
The GitHub tag and the geth.ethereum.org/downloads page list the same items. Default GOGC moves from 20 to 50. Operators who want the prior setting can still pass --gogc=20. Pebble v2 becomes the supported key-value store when a node starts from scratch. An existing database stays on Pebble v1 until the operator runs geth db pebble-upgrade.
Sparse blobpool cuts memory use for blob transactions. The v0 blob sidecars are removed from the pool. A new --rpc.http-body-limit flag appears. The --override.amsterdam flag lets operators test the ongoing Amsterdam hardfork work without any mainnet activation.
Room context and streak
The daily presence on Crypto Spaces Network continues without interruption. More than one thousand consecutive sessions keep the same 5-to-7 PM EST State of Crypto slot. That run places the Geth patch into the same cadence the room already follows for execution-client updates.
The discussion treats the change as one more maintenance step operators can apply or skip. No claims link the patch to price movement on the chart. ETH sits at 2,474.66 on the provided snapshot while majors range and alts show mixed candles.
Clear separation from other clients
The release notes and downloads page keep the scope to go-ethereum only. The patch does not replace Erigon v3.6.0, Reth v2.5.1, Nethermind v1.39.3, Besu 26.8.0, Teku 26.8.0, or Lodestar v1.46.0. Each client follows its own schedule and its own backend decisions.
Operator notes
A fresh bootstrap uses Pebble v2 automatically. Legacy databases require the explicit upgrade command. The sparse blobpool and body-limit flag give execution teams smaller memory footprints without altering consensus rules. Amsterdam work stays behind the override flag for now.
The room already moved past the July 27 tag by the time later clients posted their own August updates. The streak simply folds each new release into the next daily slot without breaking the sequence.