hyperlane-xyz/hyperlane-monorepo @hyperlane-xyz/cli@35.0.0

on GitHub

Minor Changes

• 44aa432: Added a new hyperlane warp balances CLI command that displays token balances for each leg of a warp route. Fixed EvmHypRebaseCollateralAdapter.getBridgedSupply to return the underlying asset amount (previously returned raw vault shares). Added EvmHypOwnerCollateralAdapter that reads assetDeposited directly from HypERC4626OwnerCollateral, and routed WarpCore.getTokenCollateral through getBridgedSupply for ERC4626 collateral standards so destination-collateral checks and balance display no longer report zero for yield-bearing vault routes.

• 631d7e7: ICoreAdapter.extractMessageIds was made async (returns Promise). Callers must add await at call sites.

  AleoCoreAdapter extracted message IDs by querying on-chain mappings. Because Aleo's mailbox nonce counter is a single shared mapping entry, at most one dispatch is accepted per block; a confirmed transaction with type "execute" was the accepted dispatch, and the dispatched nonce is mailbox.nonce - 1. Unlike EVM/SVM adapters that parsed receipt logs, Aleo extraction required on-chain mapping queries. Callers constructing MultiProtocolCore for an Aleo origin chain had to supply a real mailbox address (not a stub); passing no address caused extraction to return an empty result rather than throw.

  Aleo warp token writers (native, collateral, synthetic) verified that the mailbox is initialized before deploying warp tokens. Previously, running warp deploy against an uninitialized mailbox produced a cryptic "transaction rejected" error from the on-chain finalize assertion; now a clear error is thrown immediately.

• a8c9430: Enabled warp send for Aleo. When Aleo is the origin chain, the CLI now skips delivery confirmation (message ID extraction from Aleo receipts is not yet supported) instead of throwing an error.