The Agoric OpCo engineering team is pleased to publish the agoric-upgrade-16-rc0 release. This release is primarily intended to deploy the Orchestration Core feature, and fix some performance issue. This is a significant upgrade that marks a major milestone by enabling new functionality for the Agoric chain.
The following new features are included in this release:
The release contains at least the following fixes:
- #9316: Fix a memory leak that impacted commit time and resulted in missed blocks
- #9418: State-sync export would temporarily stall the node while initiating a snapshot resulting in missed blocks
- #9100: Make the
snapshots exportcommand usable - #9424: Some options like
iavl-disable-fastnodewere not applied - #9179: Avoid unnecessary rebuilds when invoking
agd
The full set of changes in this release can be found at #9588. While changes to vaults were implemented for this release, we recommend that they are not deployed to existing chains at this time using the corresponding basic upgrade plan name (see below).
Assuming this release satisfies all pre-release/testnet validation checks, it will be promoted to agoric-upgrade-16, and recommended for chains to upgrade from the previous agoric-upgrade-15 release. As a chain-halting upgrade, once approved, all chain validators will need to upgrade from agoric-upgrade-15 to this new version (after the chain halts due to reaching the height required in a governance proposal).
State-sync
As a change from previous releases, state-sync snapshots now only include minimal data to restore a node. However there are still continued performance issues related to state-sync. In particular, we've observed that on some deployments, the snapshot taking and restoring process can take multiple hours, require about 20GB of temporary free disk space, and 16GB of memory.
In this release, the snapshots export agd command has been fixed, and can now be used to generate a snapshot export of the current application state (while the node is not running). Combined with with other snapshots commands and the tendermint bootstrap-state command, this can be used to restore a node (state-sync pruning) without having to connect the node to the p2p network.
Handling of the iavl-disable-fastnode option
A bug in agoric-upgrade-14 and agoric-upgrade-15 resulted in this configuration option to be ignored, and default to false. As such all nodes will have created a "fast node" index, even if the option was explicitly set to true in the config. This release now honors the option.
Cosmos Upgrade Handler Name
In this release, the naming of cosmos upgrade handlers has changed to conditionally apply an upgrade to vaults contracts pre-configured for some well known deployments. Below are the cosmos upgrade handler names for this release. These names can be used in governance proposals to deploy this upgrade.
- "mainnet" (agoric-3 chain):
agoric-upgrade-16-main - "devnet" (agoricdev-23 chain):
agoric-upgrade-16-devnet - "basic":
agoric-upgrade-16-basic
Tags
Below is the git information related to this software release. Note the git tag does not exactly match the cosmos upgrade handler name.
Git Tag: agoric-upgrade-16-rc0
Git Commit: 94e82e6d6234466f6c06b56caf072fdd32876807
@agoric/cosmos package version: 0.35.0-u16.0
Docker: ghcr.io/agoric/agoric-sdk:44
As shown in go.mod this release is based on:
ibc-go v6.3.1
cosmos-sdk v0.46.16
cometbft v0.34.30
How to upgrade
Presuming that your node is running agoric-upgrade-15, once the upgrade height for a subsequent proposal to upgrade to agoric-upgrade-16-rc0 has been reached, your node will halt automatically allowing you to upgrade the agoric stack.
Prerequisites
Install supported versions of Go, Node.js, and a compiler such as gcc or clang as documented in the README.
Building
# (stop the agd service)
cd agoric-sdk
git fetch --all
git checkout agoric-upgrade-16-rc0
git clean -xdf && git submodule foreach --recursive git clean -xfd
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.