Repository navigation
v1.7.1
v1.7.1
A rolling patch. No halt, no GovDAO proposal, no version floor: nothing nodes agree on changes, so each operator switches whenever convenient. Cut on the same commit as v1.7.1-rc.1, which onyx ran first.
Released from chain/mainnet at 83431a7f0. Previous release: v1.7.0. Every release mainnet has run is in its upgrade ledger.
Who should run it: mainnet operators, whenever convenient; nodes on v1.7.0 and v1.7.1 run the same chain and peer with each other, so validators can move one at a time. Onyx stays on v1.7.1-rc.1, the same code.
What changes
- Release binaries (#6450): the Linux amd64 binaries are built in an
ubuntu:22.04container, so they start on glibc 2.35 or newer (Ubuntu 22.04, Debian 12);v1.7.0's needed 2.38. A release step refuses any Linux binary that needs more. - Blocks and p2p (#6486): stored and synced blocks are checked more strictly before use; each connection bounds the bytes it buffers for sending, as it already did for receiving; a peer's advertised address must be an IP address.
- RPC and queries (#6486): JSON-RPC batches hold at most 1000 requests by default; VM query answers are capped at 1 MiB;
unconfirmed_txscaps the transaction bytes of one answer; the number of parallel queries scales with free memory. - VM (#6486, #6469): the realm save walk handles an unescaped cycle; realm and run path checks test a cheap prefix first, about 20% off render queries.
- Transactions (#6399, in #6486): Go clients leave a master signature's zero session address off the wire, so such a transaction is 42 to 43 bytes smaller. Nodes accept both encodings.
- Clients (#6285, #6486): the RPC HTTP client keeps the path of an endpoint served behind a prefix; gnokey simulates a transaction with zeroed signatures unless it carries code.
- gnoweb (#6424, #6486): no data race on the form title caser; the gnokey command a page offers only uses an exported function and a canonical
.send. - gnokms and gnobro (#6486): the remote signer serves one connection at a time; gnobro caps the terminal size and the sessions one SSH client opens.
Operators, watch for
- gnoland:
- New config fields:
p2p.max_send_buffer_bytes(20 MB by default) andrpc.max_batch_requests(1000 by default, 0 for no limit; a larger batch is refused whole). p2p.max_recv_buffer_bytesandp2p.max_send_buffer_bytesmust be 0 or at least 8,454,144 bytes, one maximum block response: a smaller positive value stops the node at startup. The 20 MB defaults pass.vm/qrender,vm/qeval,vm/qeval_json,vm/qfuncs,vm/qfileandvm/qdocanswer an error in place of a result over 1 MiB.- Hostnames in
persistent_peers,seedsandexternal_addressstill resolve; what a node advertises is its IP, asv1.7.0does. - The address book gains a
last_connectedfield, whichv1.7.0ignores. - The
linux_amd64binary starts on glibc 2.35 or newer.
- New config fields:
- gnokey and gnoclient users: a transaction signed with a master key gets a different hash than the one
v1.7.0's gnokey gives it; tools that re-encode transactions compute the new hashes. A--remoteURL with a path keeps it. - gnokms: a second validator connection waits until the first closes.
- gnoweb: nothing to change.
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.7.1 |
sha256:2476951bf2a1c4f4478ee7f965291346a592f20fae790cfdbceddfaecca5a9d6 |
ghcr.io/gnolang/gno/gnoweb:v1.7.1 |
sha256:507375e3a192e27fd91960d6bc591aec42ae89d2cc1d4f79ceff7ebb7e40e414 |
ghcr.io/gnolang/gno/gnofaucet:v1.7.1 |
sha256:dc2d48dd9dc0adc5b733ba32c85b67ed170b73888945cc69c3ac391bfa2b0532 |
ghcr.io/gnolang/gno/gnokey:v1.7.1 |
sha256:6c771b2e631ffef8eebcf8957f64ffc353f84b48c512d93dcf916c017354c923 |
ghcr.io/gnolang/gno/gno:v1.7.1 |
sha256:09cc4323f517d7b60820f49654063c6c10355d81c438444a28e88edace75f5fc |
ghcr.io/gnolang/gno/gnodev:v1.7.1 |
sha256:1c062b4e3d506538d15829678f6aae35697b3133784611d8f09cc49937e9cfb9 |
ghcr.io/gnolang/gno/gnocontribs:v1.7.1 |
sha256:f051c8bdfb30ca7a68809ad9c52e558c20ec8629992e5ff8b7814d26815412b9 |
ghcr.io/gnolang/gno/gpao:v1.7.1 |
sha256:eee7c4ea220e8df1f3028cfc60e42a684b44c7ec68105d7bb429fb049eb89349 |
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.7.1 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.7.1
# cosign v3 or later: the signatures are in the Sigstore bundle format
cosign verify ghcr.io/gnolang/gno/gnoland:v1.7.1 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity https://github.com/gnolang/gno/.github/workflows/release-docker.yml@refs/tags/v1.7.1Changes since v1.7.0
Compare. #6486 was merged into chain/mainnet; every other commit is a cherry-pick from master. The full list, with what was left out and why, is in #6485.
Release tooling and docs on chain/mainnet since v1.7.0, no node code: releases publish held and are promoted once mainnet switches (#6429); VALIDATOR.md notes that v1.7.0's Linux amd64 gnoland needs glibc 2.38.