The Agoric OpCo engineering team is pleased to publish the agoric-upgrade-15 release. This release is primarily intended to better isolate CometBFT queries from in-consensus processing, providing more stability for high-throughout RPC node operators.
The following new features are included in this release:
- #9224: add a feature flag to use the CometBFT "LocalClient"
The release contains at least the following fixes:
- #9239: enhance smart wallet behavior when invitation creation fails
- #9276: Event history contains duplicate objects
The full set of changes in this release can be found at #9268.
This release has satisfied all pre-release/testnet validation checks, and is now recommended for chains to upgrade from the previous agoric-upgrade-14 release. As a chain-halting upgrade, once approved, all chain validators will need to upgrade from agoric-upgrade-14 to this new version (after the chain halts due to reaching the height required in a governance proposal).
Since the agoric-upgrade-11 release, state-sync snapshots include more data than before. Nodes which have inadvertently pruned this data (e.g. those created from a state-sync before the agoric-upgrade-11 release) will not be able to produce such snapshots, and will need to be restored from state-sync. We are aware of continued performance issues related to state-sync. In particular, we've observed that on some deployments, the current implementation can require 100 GB of temporary free disk space and 16GB of memory.
Below is the cosmos upgrade handler name for this release. This is the name that can be used in governance proposals to deploy this upgrade.
Cosmos Upgrade Handler Name: agoric-upgrade-15
Below is the git information related to this software release. Note the git tag does not always match the cosmos upgrade handler name.
Git Tag: agoric-upgrade-15
Git Commit: 734e8635002e01b3e27477e93998dda942c7fae8
@agoric/cosmos package version: 0.35.0-u15.0
Docker: ghcr.io/agoric/agoric-sdk:43
As shown in go.mod this release is based on:
ibc-go v6.2.1
cosmos-sdk v0.46.16
cometbft v0.34.30
How to upgrade
Presuming that your node is running agoric-upgrade-14, once the upgrade height for a subsequent proposal to upgrade to agoric-upgrade-15 has been reached, your node will halt automatically allowing you to upgrade the agoric stack.
Prerequisites
Install Go 1.20.2 or higher, Node.js 16 or 18, and clang 10 or gcc 10.
Building
# (stop the agd service)
cd agoric-sdk
git fetch --all
git checkout agoric-upgrade-15
git clean -xdf
yarn install
yarn build
(cd packages/cosmic-swingset && make)
# (start the agd service)
Do not copy the agd script or Go binary to another location. If you would like to have an executable agd in another location, then create a symlink in that location pointing to agoric-sdk/bin/agd.
Troubleshooting repoconfig.sh: No such file or directory
Unlike typical cosmos-sdk chains where the daemon is a single executable file, Agoric's use of cosmos-sdk depends on many components of agoric-sdk at runtime. Copying agd to /usr/local/bin or the like is unlikely to produce a working installation. For more detail, see: #7825
Troubleshooting Cannot find dependency ... in systemd
If you have LimitNOFILE=4096 in your systemd unit file, change it to LimitNOFILE=65536. For more detail, see #7817
Specifying --upgrade-info for the software upgrade proposal
The ./scripts/gen-upgrade-proposal.sh is designed to aid in composing a agd tx submit-proposal software-upgrade ... command. In particular, it captures package checksums to verify integrity of downloaded software.