agoric-upgrade-22b

The Agoric OpCo engineering team has published the agoric-upgrade-22b patch release. This release is hot patch to address the agoric-3 chain halt at block 22152552. It can be applied without a coordinated upgrade on any chains running the agoric-upgrade-22 upgrade.

The full set of changes in this release can be found at #12135. And reviewed in detail at agoric-upgrade-22a...agoric-upgrade-22b.

Please note this release is incompatible with Node.js 22. Use Node.js 20 instead

Cosmos Upgrade Handler Name

As a patch, this release does not contain a new upgrade handler name. It should be applied without a governance proposal.

Tags

Below is the git information related to this software release. Note the git tag does not always match the cosmos upgrade handler name.

Please note that the @agoric/cosmos package version did not change in this patch release.

Git Tag: agoric-upgrade-22b
Git Commit: d15cbb93a8c1e96b364de7d961909ff1199876e5
@agoric/cosmos package version: v0.35.0-u22.1
Docker: ghcr.io/agoric/agoric-sdk:69

As shown in go.mod this release is based on:

ibc-go v8.7.0
cosmos-sdk v0.50.14
cometbft v0.38.17

How to upgrade

Validators should use this agoric-upgrade-22b version of the software instead of agoric-upgrade-22 or agoric-upgrade-22a for any chains that upgrade to the agoric-upgrade-22 upgrade name.

Validators should start using this agoric-upgrade-22b software for any chains that are already running the agoric-upgrade-22 upgrade.

Prerequisites

Install supported versions of Go, Node.js, and a compiler such as gcc or clang as documented in the README.

Please note this release is incompatible with Node.js 22. Use Node.js 20 instead

Make sure that the environment running the agd service has the same Node.js version as the environment used for building. In particular, if using nvm to manage Node.js version, the service environment should enable nvm and use the same version.

Building

# (stop the agd service)
cd agoric-sdk
git fetch --all
git checkout agoric-upgrade-22b
git clean -xdf && git submodule foreach --recursive git clean -xdf
./bin/agd build
# (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 module ... was compiled against a different Node.js version and SyntaxError issues

The agd service is not using the same version of Node.js as the one used when building. The most likely cause is that nvm was used to manage the Node.js version in the shell when building. Either install the required version of Node.js globally using the system's package manager, or enable nvm in the environment of the agd service.

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 yarn: command not found or error This project's package.json defines "packageManager": "[email protected]". However the current global version of Yarn is 1.22.22

Generally, running corepack enable before running yarn install will resolve this issue. But if the issue persists, following corepack enable with corepack prepare [email protected] --activate helps resolve the issue. Replace 4.9.x with the actual version.

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

Ymax v0.3.2-beta

Build Notes: Contract Bundle

contract bundle hash from CI job:

b1-ae002a5e194361653488f06b813ac4b30d142dbebc8a1f29be8d31446fa3fb2bf7a0e323388b798a2fe77e82c7f4c0dcef78f3e4c5fc2bfc52ac2704976a0998

contract addresses: (to add later, along with privateArgs if needed)

What's Changed

since ymax-v0.3.1-beta:

• Fix: Remove automatic flow unwinding by @dtribble in #12129
• fix!: obsolete netTransfers - positive assumption is faulty by @dckc in #12130
• fix(ymax-planner): Run with 6-second heartbeats by @gibson042 in #12128
• chore: Suggestions from #12123 review by @gibson042 in #12124

Full Changelog: ymax-v0.3.1-beta...ymax-v0.3.2-beta

Ymax v0.3.1-beta

Build Notes: Contract Bundle

contract bundle hash:

agoric-sdk/multichain-testing/ymax-ops$ make clean && make
...
b1-8a009656e9dd92b33146eaa69e6b9555ffd0ea87821cf15d550df728ba3986a9f22f6dde5ed56fddf293388550504b3c6551b583efdb56cf784016eedd879e23

contract addresses:

$ cat ,privateArgsOverrides.json | jq '.contracts [].factory'
"0x51e589D94b51d01B75442AE1504cD8c50d6127C9"
"0x13cA288486f2bb6B3619c5fd6A2917Ec98a41E7f"
"0x724fB9Fd9876d12Da33223C84E7Abf46fFc159C1"
"0x6ca3e8BFe9196A463136cB2442672e46BBe00BCc"
"0x6ca3e8BFe9196A463136cB2442672e46BBe00BCc"

What's Changed

since ymax-v0.3.0-beta:

• Fix step ordering by changing back to jsLPSolver by @dtribble in #12123

Full Changelog: ymax-v0.3.0-beta...ymax-v0.3.1-beta

Ymax v0.3.0-beta

Build Notes: Contract Bundle

contract bundle hash:

agoric-sdk/multichain-testing/ymax-ops$ make clean && make
...
b1-8a009656e9dd92b33146eaa69e6b9555ffd0ea87821cf15d550df728ba3986a9f22f6dde5ed56fddf293388550504b3c6551b583efdb56cf784016eedd879e23

What's Changed

since ymax-v0.2.0-beta

• chore: listen for MultiCallStatus events for pending gmp tx by @rabi-siddique in #12049
• fix(ymax-planner): Allow target weight of zero by @gibson042 in #12050
• chore(ymax-planner): Annotate plan errors with currentBalances by @gibson042 in #12051
• feat(client-utils): Add SigningSmartWalletKit reflection methods by @gibson042 in #12033
• fix(portfolio-contract): consume Access token by @dckc in #12052
• feat(ymax-planner): Submit steps for a flow using a type-aware resolvePlan via wallet store reflection by @gibson042 in #12054
• feat: deposit, rebalance w planner by @dckc in #12016
• feat(ymax-planner): Replace tx-based deposit response with flow-based deposit/withdraw submission by @gibson042 in #12039
• feat(ymax-tool): REPL by @dckc in #12057
• chore(ymax-planner): Instruct nodemon to restart upon crash by @gibson042 in #12061
• feat(ymax planner): Support "ymax1" contract by @gibson042 in #12063
• chore: update factory addr for Arbitrum and Avalanche by @rabi-siddique in #12069
• Update Base Sepolia Factory Contract Address by @amessbee in #12070
• ymax1 Support in ymax tools by @amessbee in #12000
• fixes: Agoric/agoric-private#415 by @dtribble in #12071
• Add fee: for EVM depositForBurn invocations steps by @dtribble in #12073
• chore: ymax1 deployment tweaks by @dckc in #12072
• fix(ymax-planner): get USDN balance using uusdn denom by @dckc in #12075
• chore: update factory contract addresses by @rabi-siddique in #12086
• feat: update LP solver graph to establish direct edges from EVM to Agoric to support the use of NFA by @LuqiPan in #12078
• fix(portfolio-contract): Propagate graph arc minimum flow into LP solver input by @gibson042 in #12084
• fix!: use Noble forwarding for CCTP from EVM by @dckc in #12082
• portfolio vstorage interfaces available externally by @turadg in #12092
• chore: finetuned gas estimates by @amessbee in #12076
• Refactor internal marshal utils by @mhofman in #12096
• chore: resolve incoming CCTP using NFA by @dckc in #12088
• chore(ymax-contract): get transferChannels synchronously by @dckc in #12100
• chore(portfolio-contract): use counterpartyChannelId for NFA by @dckc in #12102
• chore(portfolio-contract): counterPartyChannelId for CCTP_TO_AGORIC by @dckc in #12103
• chore: eliminate logic related to resolving CCTP transfers from EVM to Noble ICA by @rabi-siddique in #12098
• chore(resolver): dont process CCTP_TO_AGORIC transactions by @rabi-siddique in #12105
• chore(resolver): switch to using WebSocketProvider by @rabi-siddique in #12106
• fix(orchestration): await async-flow wakening by @mhofman in #12101
• Optimize board by @mhofman in #12085
• refactor: update search window of lookback mode by @rabi-siddique in #12040
• portfolio-api type improvements by @turadg in #12117
• chore: reduce Axelar estimate padding to 10% rather than 300% by @dtribble in #12118
• fix(portfolio-contract): Start a flow when openPortfolio includes an initial deposit by @gibson042 in #12115

Full Changelog: ymax-v0.2.0-beta...ymax-v0.3.0-beta

agoric-upgrade-22a

The Agoric OpCo engineering team is pleased to publish the agoric-upgrade-22a patch release. This release is a security fix to address GHSA-hrhf-2vcr-ghch. It can be applied without a coordinated upgrade.

The full set of changes in this release can be found at #12099. And reviewed in detail at agoric-upgrade-22...agoric-upgrade-22a.

Cosmos Upgrade Handler Name

As a patch, this release does not contain a new upgrade handler name. It should be applied without a governance proposal.

Tags

Below is the git information related to this software release. Note the git tag does not always match the cosmos upgrade handler name.

Please note that the @agoric/cosmos package version did not change in this patch release.

Git Tag: agoric-upgrade-22a
Git Commit: 4e121c2c81e2dc188fd700abf4a7f88c3f096d2f
@agoric/cosmos package version: v0.35.0-u22.1
Docker: ghcr.io/agoric/agoric-sdk:68

As shown in go.mod this release is based on:

ibc-go v8.7.0
cosmos-sdk v0.50.14
cometbft v0.38.17

How to upgrade

Validators should use this agoric-upgrade-22a version of the software instead of agoric-upgrade-22 for any chains that upgrade to the agoric-upgrade-22 upgrade name.

Validators should start using this agoric-upgrade-22a software for any chains that are already running the agoric-upgrade-22 upgrade.

Prerequisites

Install supported versions of Go, Node.js, and a compiler such as gcc or clang as documented in the README.

Make sure that the environment running the agd service has the same Node.js version as the environment used for building. In particular, if using nvm to manage Node.js version, the service environment should enable nvm and use the same version.

Building

# (stop the agd service)
cd agoric-sdk
git fetch --all
git checkout agoric-upgrade-22a
git clean -xdf && git submodule foreach --recursive git clean -xdf
./bin/agd build
# (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 module ... was compiled against a different Node.js version and SyntaxError issues

The agd service is not using the same version of Node.js as the one used when building. The most likely cause is that nvm was used to manage the Node.js version in the shell when building. Either install the required version of Node.js globally using the system's package manager, or enable nvm in the environment of the agd service.

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 yarn: command not found or error This project's package.json defines "packageManager": "[email protected]". However the current global version of Yarn is 1.22.22

Generally, running corepack enable before running yarn install will resolve this issue. But if the issue persists, following corepack enable with corepack prepare [email protected] --activate helps resolve the issue. Replace 4.9.x with the actual version.

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

Ymax v0.2.0-beta

This release supports control of a ymax1 beta contract, intended to be more stable than the ymax0 alpha.

CoreEval Artifacts

Attached find 3 bundles and 4 pairs of permit/script evals. They were extracted from ci artifacts as explained in a comment on PR12038. Then eval-ymax0-control.js was replaced by eval-ymax0-control-main-z928.js, which has the mainnet ymax1 contractControl address. Likewise for eval-ymax0-control-main-nmcq.js.

What's Changed

selected changes since https://github.com/Agoric/agoric-sdk/releases/tag/ymax-v0.1.4-alpha b2cdd8c5379:

• feat: publish info on pending GMP txs by @frazarshad in #11856
• fix: clean up portfolio parseInboundPacket and noisy logged errors by @michaelfig in #11876
• chore(docs): add sequence diagram for withdraw by @LuqiPan in #11843
• feat(portfolio-contract): contractAccount for paying BLD fees by @dckc in #11882
• feat(portfolio-contract): pay BLD fees from contractAccount by @dckc in #11884
• chore: resolve cctp to noble txs by @frazarshad in #11872
• chore(ymax-planner): monitor and resolve transfers to a noble account by @rabi-siddique in #11871
• feat(orchestration): only treat localchain.queryMany truthy result.error as failure by @michaelfig in #11887
• fix: Make Resolver Registry Upgradable by @amessbee in #11858
• feat(client-utils): sendBridgeAction supports fee param by @dckc in #11868
• chore: add sender address verification for Axelar GMP transactions by @rabi-siddique in #11890
• feat(ymax-planner): Account for Axelar Cosmos-EVM fees by @gibson042 in #11914
• feat(client-utils): Support FQDNs in AGORIC_NET for parseNetworkSpec and fetchNetworkConfig/fetchEnvNetworkConfig by @gibson042 in #11926
• Ymax Config: Adding Addresses for new Protocols by @amessbee in #11920
• feat(ymax-planner): Respond to portfolio-level vstorage events by @gibson042 in #11929
• Adding new Beefy Protocols by @amessbee in #11938
• docs(portfolio-contract): updated high level system design by @LuqiPan in #11941
• fix(ymax-planner): Treat only direct children of published.ymax0.portfolios as portfolio paths by @gibson042 in #11939
• chore: resolve pending transactions via historical logs by @rabi-siddique in #11915
• chore: add alchemy rpc for Base by @rabi-siddique in #11951
• Add Arb/Base Sepolia factory address by @amessbee in #11944
• avoid awkward async callback for each step in ymax flow by @dckc in #11950
• fix: subscribe to NewBlock events instead of NewBlockHeader by @rabi-siddique in #11959
• fix: handle errors creating remote accounts by @Copilot in #11946
• feat!: vstorage preview of ymax steps by @dckc in #11963
• feat!: ymax portfolio tracks policyVersion by @dckc in #11917
• feat(ymax-planner)!: Submit plans with policyVersion and rebalanceCount by @gibson042 in #11973
• chore(portfolio-contract): bump gmp fees to 20 BLD by @LuqiPan in #11970
• feat(ymax-planner): Calculate steps by linear programming over a model of the blockchain network by @dtribble in #11932
• support custom signing data in SmartWalletKit by @turadg in #11986
• chore: added gas estimation api to planner by @frazarshad in #11953
• feat!: withdraw in coordination with ymax planner by @dckc in #11995
• chore!(portfolio-contract): add stateShape to the 4 exos by @dckc in #12015
• feat(portfolio-contract): creatorFacet.withdrawFees by @dckc in #11991
• feat(ymax-planner): Use flow-aware resolvePlan for rebalance and withdraw by @gibson042 in #12030
• chore: estimate return gas for EVM -> Agoric by @frazarshad in #12022
• Split-up portfolio-deploy and support contract name by @mhofman in #12038

New Contributors

• @Copilot made their first contribution in #11869

Full Changelog: ymax-v0.1.4-alpha...ymax-v0.2.0-beta

agoric-upgrade-22

The Agoric OpCo engineering team is pleased to publish the agoric-upgrade-22 release. This release is primarily intended to bump cosmos-sdk to v0.50 and terminate some price feed vats.

The full set of changes in this release can be found at #11894, #11902 and #11907. And reviewed in detail at agoric-upgrade-21...agoric-upgrade-22.

This release has satisfied all pre-release/testnet validation checks, and is now recommended for chains to upgrade from the previous agoric-upgrade-21 release. As a chain-halting upgrade, once approved, all chain validators will need to upgrade from agoric-upgrade-21 to this new version (after the chain halts due to reaching the height required in a governance proposal).

State-sync

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.

Cosmos Upgrade Handler Name

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-22

Tags

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-22
Git Commit: 4c65b8ef77e246c8ed3ed9ba9286c8a34356ce37
@agoric/cosmos package version: v0.35.0-u22.1
Docker: ghcr.io/agoric/agoric-sdk:67

As shown in go.mod this release is based on:

ibc-go v8.7.0
cosmos-sdk v0.50.14
cometbft v0.38.17

How to upgrade

Presuming that your node is running agoric-upgrade-21, once the upgrade height for a subsequent proposal to upgrade to agoric-upgrade-22 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.

Make sure that the environment running the agd service has the same Node.js version as the environment used for building. In particular, if using nvm to manage Node.js version, the service environment should enable nvm and use the same version.

Building

# (stop the agd service)
cd agoric-sdk
git fetch --all
git checkout agoric-upgrade-22
git clean -xdf && git submodule foreach --recursive git clean -xdf
./bin/agd build
# (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 module ... was compiled against a different Node.js version and SyntaxError issues

The agd service is not using the same version of Node.js as the one used when building. The most likely cause is that nvm was used to manage the Node.js version in the shell when building. Either install the required version of Node.js globally using the system's package manager, or enable nvm in the environment of the agd service.

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 yarn: command not found or error This project's package.json defines "packageManager": "[email protected]". However the current global version of Yarn is 1.22.22

Generally, running corepack enable before running yarn install will resolve this issue. But if the issue persists, following corepack enable with corepack prepare [email protected] --activate helps resolve the issue. Replace 4.9.x with the actual version.

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.

agoric-upgrade-22-rc1

The Agoric OpCo engineering team is pleased to publish the agoric-upgrade-22-rc1 release. This release is primarily intended to bump cosmos-sdk to v0.50 and terminate some price feed vats.

The full set of changes in this release can be found at #11894, #11902 and #11907. And reviewed in detail at agoric-upgrade-21...agoric-upgrade-22-rc1.
For changes between rc0 and rc1, see agoric-upgrade-22-rc0...agoric-upgrade-22-rc1.

Assuming this release satisfies all pre-release/testnet validation checks, it will be promoted to agoric-upgrade-22, and recommended for chains to upgrade from the previous agoric-upgrade-21 release. As a chain-halting upgrade, once approved, all chain validators will need to upgrade from agoric-upgrade-21 to this new version (after the chain halts due to reaching the height required in a governance proposal).

State-sync

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.

Cosmos Upgrade Handler Name

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-22

Tags

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-22-rc1
Git Commit: 4c65b8ef77e246c8ed3ed9ba9286c8a34356ce37
@agoric/cosmos package version: v0.35.0-u22.1
Docker: ghcr.io/agoric/agoric-sdk:67

As shown in go.mod this release is based on:

ibc-go v8.7.0
cosmos-sdk v0.50.14
cometbft v0.38.17

How to upgrade

Presuming that your node is running agoric-upgrade-21, once the upgrade height for a subsequent proposal to upgrade to agoric-upgrade-22-rc1 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.

Make sure that the environment running the agd service has the same Node.js version as the environment used for building. In particular, if using nvm to manage Node.js version, the service environment should enable nvm and use the same version.

Building

# (stop the agd service)
cd agoric-sdk
git fetch --all
git checkout agoric-upgrade-22-rc1
git clean -xdf && git submodule foreach --recursive git clean -xdf
./bin/agd build
# (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 module ... was compiled against a different Node.js version and SyntaxError issues

The agd service is not using the same version of Node.js as the one used when building. The most likely cause is that nvm was used to manage the Node.js version in the shell when building. Either install the required version of Node.js globally using the system's package manager, or enable nvm in the environment of the agd service.

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 yarn: command not found or error This project's package.json defines "packageManager": "[email protected]". However the current global version of Yarn is 1.22.22

Generally, running corepack enable before running yarn install will resolve this issue. But if the issue persists, following corepack enable with corepack prepare [email protected] --activate helps resolve the issue. Replace 4.9.x with the actual version.

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.

agoric-upgrade-22-rc0

The Agoric OpCo engineering team is pleased to publish the agoric-upgrade-22-rc0 release. This release is primarily intended to bump cosmos-sdk to v0.50 and terminate some price feed vats.

The full set of changes in this release can be found at #11894 and #11902, and reviewed in detail at agoric-upgrade-21...agoric-upgrade-22-rc0.

Assuming this release satisfies all pre-release/testnet validation checks, it will be promoted to agoric-upgrade-22, and recommended for chains to upgrade from the previous agoric-upgrade-21 release. As a chain-halting upgrade, once approved, all chain validators will need to upgrade from agoric-upgrade-21 to this new version (after the chain halts due to reaching the height required in a governance proposal).

State-sync

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.

Cosmos Upgrade Handler Name

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-22

Tags

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-22-rc0
Git Commit: 83a42d0f343b01448a918631dce159b5bdb69b7e
@agoric/cosmos package version: v0.35.0-u22.0
Docker: ghcr.io/agoric/agoric-sdk:66

As shown in go.mod this release is based on:

ibc-go v8.7.0
cosmos-sdk v0.50.14
cometbft v0.38.17

How to upgrade

Presuming that your node is running agoric-upgrade-21, once the upgrade height for a subsequent proposal to upgrade to agoric-upgrade-22-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.

Make sure that the environment running the agd service has the same Node.js version as the environment used for building. In particular, if using nvm to manage Node.js version, the service environment should enable nvm and use the same version.

Building

# (stop the agd service)
cd agoric-sdk
git fetch --all
git checkout agoric-upgrade-22-rc0
git clean -xdf && git submodule foreach --recursive git clean -xdf
./bin/agd build
# (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 module ... was compiled against a different Node.js version and SyntaxError issues

The agd service is not using the same version of Node.js as the one used when building. The most likely cause is that nvm was used to manage the Node.js version in the shell when building. Either install the required version of Node.js globally using the system's package manager, or enable nvm in the environment of the agd service.

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 yarn: command not found or error This project's package.json defines "packageManager": "[email protected]". However the current global version of Yarn is 1.22.22

Generally, running corepack enable before running yarn install will resolve this issue. But if the issue persists, following corepack enable with corepack prepare [email protected] --activate helps resolve the issue. Replace 4.9.x with the actual version.

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.

YMax Alpha 1.4

This 0.1.4-alpha release primarily adds robustness to the ymax contract control component:

• fix(portfolio-deploy): handle terminated ymax0Kit.instance by @dckc in #11838

Note: the postalService contract bundle is unchanged from the 1.3 release (b1-9486f1a9b190fd5aebaeb371674567e03813d7e63f16f1c94e8ea4722eeb8d696dac171b7ed144edc2520eb49ede449205f5866835249f75ca940547665e9073).

What's Changed

• docs(portfolio-contract): rename to ymax planner, add rebalance diagram by @LuqiPan in #11760
• docs: add subscription flow sequence diagram by @rabi-siddique in #11777
• feat(ymax-planner): Establish subscriptions before querying initial state by @gibson042 in #11766
• signing smart wallet kit by @turadg in #11778
• docs(portfolio-contract): add details for makeAccount by @LuqiPan in #11772
• fix: use buildGasPayload for remote account creation by @rabi-siddique in #11768
• minor fixes in axelar-gmp contract to run integration tests by @rabi-siddique in #11784
• chore(client-utils): codegen handles gnu sed by @mhofman in #11783
• ymax-planner cleanup by @turadg in #11765
• feat: Adding CCTP tx Ack Handler by @amessbee in #11713
• feat: adding a cctp status to vstorage so it is readable by ymax planner by @frazarshad in #11714
• chore: add ymax support for ethereum by @rabi-siddique in #11785
• chore: ymax planner facet, depositAddress by @dckc in #11759
• fix: align vstorage posted data with expected resolver handler status by @rabi-siddique in #11815
• verify codegen idempotence by @turadg in #11819
• feat: handle GMP and CCTP transactions off-chain by @rabi-siddique in #11752
• deployment of ymax planner by @turadg in #11796
• Resolver refactors and improvements by @rabi-siddique in #11830
• chore: setup to the resolver handler to manage gmp transactions by @rabi-siddique in #11818
• chore: return tx ID from registerTransaction by @rabi-siddique in #11836
• fix(portfolio-deploy): handle terminated ymax0Kit.instance by @dckc in #11838

Full Changelog: ymax-v0.1.3-alpha...ymax-v0.1.4-alpha