ymax-v0.3.2608-beta2

What's Changed

• Restrict swaps to reward tokens by @michaelfig in #12831
• chore(node): switch defaults to Node 24 by @michaelfig in #12832
• Improved EIP-712 fields validation with optional support by @mhofman in #12829
• Wire auto-claimRewards by @mhofman in #12858
• Remove Array.from({ length }) by @mhofman in #12860

Full Changelog: ymax-v0.3.2608-beta1...ymax-v0.3.2608-beta2

Ymax v0.3.2608-beta1

What's Changed

• feat(portfolio-api): Improve the chainOf fallback path by @gibson042 in #12824
• feat: add claim rewards functionality for morpho vaults by @frazarshad in #12701
• feat: add new morpho vaults by @frazarshad in #12833
• feat: claim rewards from compound by @frazarshad in #12707
• feat: add claimRewards for aave by @frazarshad in #12711

Full Changelog: ymax-v0.3.2607-beta5...ymax-v0.3.2608-beta1

agoric-upgrade-23a

The Agoric OpCo engineering team is pleased to publish the agoric-upgrade-23a release. This release is intended to handle invalid JSON upgrade info. The orginal release agoric-upgrade-23 was primarily intended to upgrade cosmos-sdk to v0.53, including changes to support the new version, many other enhancements, and bug fixes.

The full set of changes in this release can be found in detail at agoric-upgrade-22c...agoric-upgrade-23a.

This release is recommended for chains to upgrade from the previous agoric-upgrade-22 line of releases (including 22a, 22b, and 22c). As a chain-halting upgrade, once approved, all chain validators will need to upgrade from agoric-upgrade-22 to this new version (after the chain halts due to reaching the height required in a governance proposal). It supersedes and can be applied instead of agoric-upgrade-23

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

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-23a
Git Commit: cc25a298dc15a17a1f7af6bbafbc45a706f7804e
@agoric/cosmos package version: v0.36.0-u23.1
Docker: ghcr.io/agoric/agoric-sdk:76

As shown in agd version --long (and golang/cosmos/go.work), this release is based on:

ibc-apps v10.1.1-alpha.agoric.0
ibc-go v10.5.0-alpha.agoric.4
cosmos-sdk v0.53.6-alpha.agoric.1
cometbft v0.38.21-alpha.agoric.1

How to upgrade

Presuming that your node is running agoric-upgrade-22, once the upgrade height for a subsequent proposal to upgrade to agoric-upgrade-23 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-23a
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 similar 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": "yarn@4.9.x". 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 yarn@4.9.x --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 upgrade software-upgrade ... command. In particular, it captures package checksums to verify the integrity of downloaded software.

ymax-v0.3.2607-beta5

New contract address added to privateArgs:

 "ERC4626_morphoHumaUsdcMain_Ethereum": "0x8aC91877b93330f52b2979a31a4879506021475c",

What's Changed

• Bump policyVersion on grant / setAutoFeatures by @mhofman in #12820
• chore: add huma usdc main vault by @frazarshad in #12822

Full Changelog: ymax-v0.3.2607-beta4...ymax-v0.3.2607-beta5

Ymax v0.3.2607-beta4

new contract address added to privateArgs:

 "ERC4626_morphoRockawayxUsdcYield_Ethereum": "0xE0181090c22579B6A217f1522cbf8c9f1F0C1965",

What's Changed

• EVM portfolio operation outcome observability by @mhofman in #12815
• chore: add rockawayx usdc yield vault by @frazarshad in #12821

Full Changelog: ymax-v0.3.2607-beta3...ymax-v0.3.2607-beta4

agoric-upgrade-23

The Agoric OpCo engineering team is pleased to publish the agoric-upgrade-23 release. This release is primarily intended to upgrade cosmos-sdk to v0.53, including changes to support the new version, many other enhancements, and bug fixes.

The full set of changes in this release can be found in detail at agoric-upgrade-22c...agoric-upgrade-23.

This release is recommended for chains to upgrade from the previous agoric-upgrade-22 line of releases (including 22a, 22b, and 22c). As a chain-halting upgrade, once approved, all chain validators will need to upgrade from agoric-upgrade-22 to this new version (after the chain halts due to reaching the height required in a governance proposal).

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

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-23
Git Commit: 1b99316a4104439cb73b906ca8452732edcdd748
@agoric/cosmos package version: v0.36.0-u23.1
Docker: ghcr.io/agoric/agoric-sdk:75

As shown in agd version --long (and golang/cosmos/go.work), this release is based on:

ibc-apps v10.1.1-alpha.agoric.0
ibc-go v10.5.0-alpha.agoric.4
cosmos-sdk v0.53.6-alpha.agoric.1
cometbft v0.38.21-alpha.agoric.1

How to upgrade

Presuming that your node is running agoric-upgrade-22, once the upgrade height for a subsequent proposal to upgrade to agoric-upgrade-23 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-23
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 similar 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": "yarn@4.9.x". 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 yarn@4.9.x --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 upgrade software-upgrade ... command. In particular, it captures package checksums to verify the integrity of downloaded software.

ymax beta: Open with grant

What's Changed

• Improve Ymax1 deployment by @mhofman in #12801
• feat: create claim rewards step by @frazarshad in #12718
• feat(portfolio-contract): Open with grant by @dckc in #12805

Full Changelog: ymax-v0.3.2607-beta2...ymax-v0.3.2607-beta3

agoric-upgrade-23-rc2

The Agoric OpCo engineering team is pleased to publish the agoric-upgrade-23-rc2 release. This release is primarily intended to upgrade cosmos-sdk to v0.53, including changes to support the new version, many other enhancements, and bug fixes.

The full set of changes in this release can be found in detail at agoric-upgrade-22c...agoric-upgrade-23-rc2.

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

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

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-23-rc2
Git Commit: 1b99316a4104439cb73b906ca8452732edcdd748
@agoric/cosmos package version: v0.36.0-u23.1
Docker: ghcr.io/agoric/agoric-sdk:75

As shown in agd version --long (and golang/cosmos/go.work), this release is based on:

ibc-apps v10.1.1-alpha.agoric.0
ibc-go v10.5.0-alpha.agoric.4
cosmos-sdk v0.53.6-alpha.agoric.1
cometbft v0.38.21-alpha.agoric.1

How to upgrade

Presuming that your node is running agoric-upgrade-22, once the upgrade height for a subsequent proposal to upgrade to agoric-upgrade-23 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-23-rc2
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 similar 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": "yarn@4.9.x". 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 yarn@4.9.x --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 upgrade software-upgrade ... command. In particular, it captures package checksums to verify the integrity of downloaded software.

Ymax v0.3.2607-beta2

This release contains reliability improvements and is expected to be promoted as the next production release of Ymax.

What's Changed

• chore(portfolio-api): Undeprecate StatusFor['portfolio'] flowCount by @gibson042 in #12777
• chore(portfolio-deploy): idempotent ymax upgrade confirm step by @dckc in #12680
• feat: decentralized ymaxControl by @dckc in #12774
• fix(ymax-planner): Support flow steps in excess of 1M USDC by @gibson042 in #12786
• feat(ymax-planner): Log recoveries after external fetch errors by @gibson042 in #12784
• chore(portfolio-api): Restore auto-rebalancing by @gibson042 in #12787
• fix(ymax-resolver): prevent one CCTP transfer from settling multiple pending txs by @rabi-siddique in #12785
• refactor(ymax-planner): Simplify tx watching by @gibson042 in #12790
• feat(ymax-planner): post to YDS /transactions by @michaelfig in #12756
• feat(ymax-planner): Auto-rebalance portfolios in parallel by @gibson042 in #12788
• chore(portfolio-contract): put swap behind experimental feature flag by @mhofman in #12795
• Remove planner submit by @mhofman in #12796
• fix(portfolio-contract): planner cannot add positions by @dckc in #12532

Full Changelog: ymax-v0.3.2607-beta1...ymax-v0.3.2607-beta2

Ymax v0.3.2607-beta1: Open with auto-rebalance, update morpho instruments

This release introduces contract support for:

• opening a portfolio with auto-features in one operation
• combined updates for published flow agent designations (breaking change)
• 3 new Morpho vaults

The signature of API methods used by delegation clients also has a breaking change, and clients will need to be updated.

The network graph is updated to avoid deposits to Morpho Alpha USDC Core Ethereum.

The resolver contains reliability improvements.

What's Changed

• chore: Sync Endo dependency versions by @turadg in #12734
• fix(planner): Use start script for planner deployment by @usmanmani1122 in #12694
• feat(ymax-planner): opt-in automated rebalancing by @michaelfig in #12743
• Published flow details by @mhofman in #12753
• feat(client-utils): Add memo/signerData support to reflectWalletStore by @gibson042 in #12755
• feat(client-utils)!: Introduce reflectWalletStore target method modifier once by @gibson042 in #12758
• Delegation params update by @mhofman in #12757
• Open with Auto-Features by @mhofman in #12761
• fix(ymax-resolver): self-heal dead EVM WebSockets to keep resolving pending txs by @rabi-siddique in #12752
• refactor(ymax-planner): Improve external request efficiency by @gibson042 in #12763
• chore(portfolio-api): Manually block deposits to Morpho Alpha USDC Core Ethereum by @gibson042 in #12764
• chore(portfolio-api): Update CCTPv2 link minimums to 1 USDC by @gibson042 in #12768
• refactor(portfolio-contract): Make better use of partialMap by @gibson042 in #12769
• feat: add addresses for new morpho v2 vaults by @frazarshad in #12767
• chore(portfolio-api): Restore auto-rebalancing by @gibson042 in #12775

Note: This is the full changelog since ymax-v0.3.2606-beta2 as the ymax-v0.3.2606-beta3 release was never deployed.

Full Changelog: ymax-v0.3.2606-beta2...ymax-v0.3.2607-beta1