ymax agent delegation - simple constraint

ymax-v0.3.2605-beta1

What's Changed

• chore(ymax-planner): retry vstorage reads during planner startup by @rabi-siddique in #12675
• chore(deps): Bump @lerna-lite/* to ~4.9.0 for OIDC support by @usmanmani1122 in #12677
• chore(portfolio-contract): restore CCTPv2 routes to prod network by @dckc in #12684
• refactor(ymax-resolver): update resolver retry helper by @rabi-siddique in #12676
• ci(after-merge): Enable npm OIDC trusted publishing on dev-canary by @usmanmani1122 in #12683
• chore(ymax-resolver): resolve pending transaction if tx status is known by @rabi-siddique in #12678
• feat: manually relay CCTPv2 in case relayer gives up by @dckc in #12686
• feat: export computeTargetBalances and prod-network for yds consumption by @samsiegart in #12679
• chore: backport agoric-upgrade-23-rc1 fixes to master by @michaelfig in #12687
• chore(deps): bump protobufjs; dedupe by @dckc in #12698
• fix(packing): keep canary version during npm publish postpack by @samsiegart in #12692
• feat: portfolio delegation - simple constraint by @dckc in #12688

Full Changelog: ymax-v0.3.2605-beta1...ymax-v0.3.2606-beta1

Ymax v0.3.2605-beta1: direct EVM->EVM chain transfers

What's Changed

• Verified Signer YMax tools by @mhofman in #12614
• test(ymax-planner): Cover chain-account target allocations by @gibson042 in #12616
• fix(ymax-resolver): retry resolver settlements on broadcast failure by @rabi-siddique in #12626
• chore: support AGORIC_REST_URL to override REST endpoint by @rabi-siddique in #12627
• fix(ymax-planner): Use a looser integer tolerance in the minor-unit LP solve by @gibson042 in #12633
• chore(ymax-resolver): poll for confirmations instead of newHeads subscription by @rabi-siddique in #12635
• chore(ymax-planner): Improve consistency and reduce redundancy in EVM watchers by @gibson042 in #12640
• refactor(ymax-planner): drop CosmosRestClient by @rabi-siddique in #12642
• feat(ymax-planner): Improve the "No feasible solution" error message for a graph with debug: true by @gibson042 in #12641
• feat(internal): Rate limiting in ymax planner when fetching pending transactions by @usmanmani1122 in #12634
• fix(ymax-planner): Update refineModel to exclude spurious flows by @gibson042 in #12645
• feat(portfolio-deploy): add release-based YMax deploy workflow by @dckc in #12622
• feat(ymax-planner): Process newest pending transactions first on startup by @usmanmani1122 in #12646
• feat(ymax-planner): Suppress movement to/from a no-deposit/no-withdraw instrument (respectively) by @gibson042 in #12652
• fix(ymax-planner): Use a looser floating-point tolerance in the major… by @gibson042 in #12665
• chore: retry watchers on transient failures by @rabi-siddique in #12668
• chore(ymax-planner): skip startup vstorage reads for already-resolved txs by @rabi-siddique in #12669
• chore(ymax-planner): add cache subcommand to tx-tool by @rabi-siddique in #12671
• chore: CCTPv2 destinationCaller for managed relayer by @dckc in #12664

Full Changelog: ymax-v0.3.2604-beta2...ymax-v0.3.2605-beta1

Note that before incarnation 35 , upgrades succeeded for incarnations 28 to 34, but the deployment ci job wasn't robust enough to capture the details about them. See #12680 to make it more robust.

agoric-upgrade-23-rc1

The Agoric OpCo engineering team is pleased to publish the agoric-upgrade-23-rc1 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-rc1.

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-rc1
Git Commit: 1147be15b0704de17204d04e2407fa3192b98a1c
@agoric/cosmos package version: v0.36.0-u23.0
Docker: ghcr.io/agoric/agoric-sdk:74

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

v0.3.YYMM-itest4

more ymax deployment testing...

v0.3.2604-itest3

fix(ymax-planner): Use a looser integer tolerance in the minor-unit L…

v0.3.2604-itest2

further integration testing of automated deployment #12622

v0.3.2604-itest1

integration testing of automated deployment #12622

Ymax v0.3.2604-beta2: smart account and USDC allocation

This Ymax release introduces support for portfolios owned by smart accounts, and USDC as an allowed allocation target.

What's Changed

• chore: allow failed state without address in PortfolioGenericRemoteAccountState by @rabi-siddique in #12596
• chore(portfolio-contract): use docs-design/ uniformly; factor out flows test mocks by @dckc in #12597
• feat(ymax-planner): Suppress too-small balance changes by @gibson042 in #12605
• speed up portfolio-contract tests by @turadg in #12550
• fix(ymax-planner): Restore too-small balance changes by @gibson042 in #12612
• EVM message handler accepts verified signer by @mhofman in #12611
• feat!(portfolio-contract): USDC instrument allocation to remote account by @dckc in #12599

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

bundle identification

b1-44adc29d79b5535aaad92b9773f14acde9169ee7b793624f6858000d063ded57e7b74f57419f7bbbbfa42c9c400edbdfc85f149c82d5b6fbe5d208776949ebb8

build-bundles job

Ymax v0.3.2604-beta1: router based remote accounts

This Ymax release introduces support for new remote account EVM contracts, paving the way for a better UX when signing Ymax portfolio operations, and enabling future upgrades of EVM based features.

What's Changed

• docs: update resolver docs by @rabi-siddique in #12548
• chore(ymax-resolver): rename sourceAddress to txIdPlaintext in OperationResult parser by @rabi-siddique in #12567
• chore: enable efficient vetted router upgrades for remote accounts by @mhofman in #12558
• chore: Minor cleanup in ymax-planner and core package comments by @gibson042 in #12588
• refactor(ymax-resolver): consolidate operation-watcher to single Alchemy subscription by @rabi-siddique in #12552
• feat(ymax-planner): use alchemy api for getting pool balances by @frazarshad in #12518
• refactor(ymax-planner): Renames to indicate Spectrum specificity by @gibson042 in #12589
• chore: update ymax0 devnet addresses by @mhofman in #12593

Full Changelog: v0.3.2603-beta2...ymax-v0.3.2604-beta1

bundle identification

b1-ada80b68358662c55c2e3ffb8da391df4b9a97bbd76d4634c8befb6d517f401538c65978fd34884f8eda128bb31b7a2f4fc6dbecf54a5bc829a5bd9f48f4945f

• build-bundles job

Ymax v0.3.2603-beta2 - concurrent processing & support for resolving router contract transactions (post-Mar 13 deploy)

What's changed

fix(ymax-planner): process pending tx events concurrently with portfolio events

chore(ymax-resolver): resolve operation events

Notes

• Builds on v0.3.2603-beta1 (rate limit retry improvements)
• Last planner deployment: March 13, 2026
• Contract changes are deployed separately