Skip to content

v1.8.0

Latest

Choose a tag to compare

@github-actions github-actions released this 17 Nov 16:52
· 4 commits to master since this release
fc79041

v1.8.0

A coordinated upgrade. Every validator halts after block H and restarts on v1.8.0: after the halt a node refuses an older binary, and before it this one (halt_min_version = v1.8.0). The halt is after block 1651500 (GovDAO proposal #19), about 2026-11-18 13:16 UTC. Cut on the same commit as v1.8.0-rc.1, which onyx ran first.

Released from chain/mainnet at fc79041f4. Previous release: v1.7.1. Every release mainnet has run is in its upgrade ledger.

Who should run it: every mainnet validator, at the halt.

What changes

  • Security fixes across consensus, block storage, the VM, p2p and RPC. They are described once mainnet runs v1.8.0.
  • Canonical transaction encoding (#6406): from the halt, a transaction whose bytes are not the canonical encoding of what it decodes to is refused, in CheckTx and DeliverTx. Clients built before v1.7.1 write such transactions: see below.
  • Queries (#6413): new rpc.allow_code_execution; false refuses the queries that run code (.app/simulate, vm/qeval, …). Default true.
  • Block storage (#6264, #6334): a block is saved with one fsync instead of two, and block sync defers its writes to ordered flush points. No stored format change.
  • gnoweb (#5421, #6411, #6448): a built-in playground; search keeps undecoded indexer rows out and lays results out as a listing; status.json reports the right height and version, and the chain ID.
  • gpao (#6180): the default approval fee drops to 0.1 GNOT.

Operators, watch for

  • Clients: from the halt, a transaction from a client built before v1.7.1 (gnokey, gnoclient, bots, scripts) is refused with tx decode error, its log ending with (upgrade your client to gno v1.7.1+). Rebuild every signer from v1.7.1 or later before the halt; v1.7.1 nodes already accept the canonical form. amino-ts 0.2.1 or later and the ts-proto clients (tm2-js-client, gno-js-client) are canonical.
  • gnoland: leave halt_height at 0 in config.toml, let the node halt, then restart on this release. New optional config.toml keys, all defaulting to today's behavior: [application] query_max_gas, query_max_alloc, query_timeout (0 uses the app defaults; query_timeout 0 derives the limit from the gas limit at 2 ns per gas: raise it on hardware slower than the calibration), and [rpc] allow_code_execution. The first render of a very large realm after the switch can exceed the query time limit once.
  • Syncing from genesis: this release cannot replay the blocks before its halt. Run v1.7.1, with GNOROOT at a checkout of v1.7.1 or its container image, up to the halt height, then this release; started from genesis, it stops within its first blocks with wrong Block.Header.AppHash. Verified on onyx on 2026-11-17 with a fresh node.
  • gnoweb: nothing to change. Move it after the halt.
  • gpao, for anyone running it themselves (gno-core's approver is GPASO, built from its own sources and moved by infra): the default --gas-fee drops from 1000000ugnot to 100000ugnot; it must cover the gas an approval asks for at 1ugnot per 1,000 gas, so an approval with --gas-wanted above 100,000,000 needs --gas-fee raised with it. Move it last, once every node runs this release.
  • Built from source, pass VERSION=v1.8.0.

Docker images

Multi-arch (linux/amd64, linux/arm64), signed keylessly by the release / docker workflow, the index and each platform image.

Image Index digest
ghcr.io/gnolang/gno/gnoland:v1.8.0 sha256:770f5b8012b32aa8f34afadc814c1132ba9734cc0f44062c81e1c701c5460337
ghcr.io/gnolang/gno/gnoweb:v1.8.0 sha256:4e5767722bfade8aafadcf6bce82244bf81e52a038a8cfd6175914b3b25ac4b9
ghcr.io/gnolang/gno/gnofaucet:v1.8.0 sha256:5994b5d3163a6b8e36d97522e728e65287fa8b53a4ef5178df953041b9dca4cf
ghcr.io/gnolang/gno/gnokey:v1.8.0 sha256:72cc643d10b28a0fbf2b5c62e867e6a6005b58f271848b958b201b3f340e0e24
ghcr.io/gnolang/gno/gno:v1.8.0 sha256:6417d49e44f5a16021b063d951ab343c5be911d5a40a743fc1467f97620c2853
ghcr.io/gnolang/gno/gnodev:v1.8.0 sha256:153a6ae86b77d1e3d442c51b7a56a3a1767dad1ed6b6d9220b30a3771ca18e3d
ghcr.io/gnolang/gno/gnocontribs:v1.8.0 sha256:b31bf4ac21f650ca120f54f9d04b34a3b21613478e7c34e0fad58f7bc4b46f82
ghcr.io/gnolang/gno/gpao:v1.8.0 sha256:e5a74fbc7e67995f80ee4cf518e1106fe1f8ee81b72b8e7ff4b193ab119e206a

Binaries

Attached below: gno, gnokey, gnoland, gnoweb and gnodev for linux and darwin, amd64 and arm64, built by the release / chain-tag workflow from this tag. CHECKSUMS.txt covers all of them, and gnoland, gnokey and gno print v1.8.0 on version. The binaries and CHECKSUMS.txt carry a build-provenance attestation.

Verify before you run it

gh attestation verify gnoland_linux_amd64 --repo gnolang/gno \
  --signer-workflow gnolang/gno/.github/workflows/release-chain-tag.yml \
  --source-ref refs/tags/v1.8.0

# cosign v3 or later: the signatures are in the Sigstore bundle format
cosign verify ghcr.io/gnolang/gno/gnoland:v1.8.0 \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --certificate-identity https://github.com/gnolang/gno/.github/workflows/release-docker.yml@refs/tags/v1.8.0

Changes since v1.7.1

Compare. The security fixes, and from master: #6406, #6413, #6264, #6334, #5421, #6411, #6448, #6180.

Docs and CI on chain/mainnet since v1.7.1, no node code: #6433, #6405, #6378, #6212, #6204, #6099, #6194, #6219, #6351, #6384, and the builder docs' package-status link (#6501).