Tag:
Branch:
Tree:
ab28721b6f
0.2.4
0.4.1
0.5.0
0.5.1
0.5.2
0.5.3
06-19-add_ci-default-test
07-01-feat_cli_Add_hyperlane_warp_apply
1.0.0-beta8
3.1.4
CODEOWNERS-ascii
Defcon023/mock_mailbox_size_check
add-delegate
aggregation-hook-improvements
ameten/non-native-token
ameten/scraper-sealevel-e2e
ameten/sealevel-payment-sequence
ancient8-eth-verify
asaj/addresses
asaj/agent-dev-env
asaj/announce
asaj/block-skew
asaj/check-middlewares
asaj/check-ownables
asaj/ci
asaj/ci-try
asaj/count-lag
asaj/debug
asaj/debug-ci
asaj/deploy
asaj/deploy-ergonomics
asaj/e2e-fast
asaj/enroll
asaj/fern
asaj/gas-profiling
asaj/hardhat
asaj/hardhat-plugin
asaj/hardhat-task
asaj/hooks
asaj/image
asaj/inbox-checkpoints
asaj/index
asaj/kathy-7
asaj/kathy-9
asaj/key-funder
asaj/lag-count
asaj/ll
asaj/metadata-debug
asaj/new-update
asaj/ownable-replicas-dev
asaj/ownership
asaj/ownerships
asaj/ownersss
asaj/pd
asaj/pi-deployer
asaj/poc
asaj/prettier
asaj/readonly
asaj/relayer-checkpoints
asaj/relayer-isms
asaj/router-govern
asaj/schnorr
asaj/schnorr-2
asaj/sdk-proposal
asaj/sealevel-inclusive
asaj/serialize
asaj/solc
asaj/sovereign
asaj/suffix
asaj/upgrade-dev-scripts
asaj/upgrade-rotate-updater
asaj/upgrades
asaj/v2-create2
asaj/v2-exploration
asaj/v2-helm
asaj/v2-main
asaj/workflows
asaj/zkevm
audit-coverage
audit-q3-2024
avious00-link-to-loglevel
avious00-typo-patch
aws-signer-retry
benchmark-multisig
buddies-main-deployment
build-ccip-server
changeset-release/main
changeset-release/release-test
checkInflight
ci-by-path
cli-2.0-beta
cli-figlet
cli-patches
core-msg-encoding
cosmos-gas-prices
cover-mailbox-100%
coverage-flake
create2-deploy
dan/aggregation-ism-rc
dan/bump-relayer-image
dan/configurable-fallback-deprio
dan/cw-types-reuse
dan/debug-cosmos-rpc
dan/e2e-fixes
dan/eip1967
dan/fast-relayer-startup-e2e
dan/fix-apechain-gas-estimation
dan/index-range-refactor
dan/injective-e2e
dan/injective-testnet-agents
dan/keypair-cosmrs
dan/local-svm-setup
dan/lower-txid-channel-size
dan/merkle-tree-hook-indexer
dan/non-evm-cli-warp-deploy
dan/osmosis-test
dan/processed-commitment-sealevel
dan/rc-relayer-profiling
dan/relayer-images-bump
dan/relayer-migrations
dan/retry-cosmos-e2e
dan/rocksdb-config
dan/rust-caching
dan/stage-agent-fixes
dan/testnet-aggregation-ism
dan/tmp-branch
dan/token-config-schema
dan/v3-e2e
dan/v3-sealevel-e2e
dan/va-urls
dan/zksync-testing
danil/validator_deployment_latest_image
deploy-create2-factory-moonbeam
deploy-ica-proxied
deploy-middlewares-1.3.1
deploy-wait
deployer-options
docs-simplifications
drew/manual_processing_config
dynamic-cli-version
eigenlayer
erc165
fallback-routing-hook-deployer
feat/hl-starknet-29-oct
feat/v3-cosmos
flexible-voting-vault
github-pr-stats
hook-agent-testing
hook-ism-contract-READMEs
injective-ism-fix
interchain-call-tests
kunal/arb-l2-hook-contracts
kunal/arb-selfrelay
kunal/arb-sepolia-deployment
kunal/ascii-art
kunal/avs-contract-deployment
kunal/avs-temp
kunal/avs-update-reward
kunal/avs-validator-check-status
kunal/bump-solana-prio-fee-further
kunal/check-msg-value-send-auth-hooks
kunal/ci-checker-warp-fix
kunal/cli-register-ci
kunal/default-hook
kunal/fraud-proof-router
kunal/ica-deployment
kunal/ica-govern-testing
kunal/igp-hook
kunal/ism-factory-warp-deploy
kunal/l2-native-bridge-hook
kunal/latest-height-merkle-root-index
kunal/manta-gas-overpayment-fix
kunal/messageIdAuth-replay-protection
kunal/native-arbitrum-hook
kunal/native-gnosis-hook
kunal/native-polygon-hook
kunal/null-metadata
kunal/op-stack-hook-custom-test
kunal/orphan-format-igp-async
kunal/ownable-caching-hook
kunal/rc-kathy-ism-config
kunal/relayer-metadata-null
kunal/revert-multisig-interface
kunal/revert-weighted-multisig-changes
kunal/rez-avs
kunal/special-case-plume-testnet
kunal/stake-weighted-ism
kunal/update-gasOracle-cron-job
kunal/update-gasOracle-deployer
kunal/v3-pr-comments-fixes
kunal/validator-el-sig-posting
kunal/validator-endpoints
kunal/value-router
kunal/verifiedMessageId-param
kunal/verify-ica
kunal/warp-route-checker
kunal/weighted-ism-relayer-change
light-optimistic
lint.only
liquidity-layer-v2
ltyu/core-apply-defaultIsm
ltyu/ezEth-swell-feeHook
ltyu/hook-config
ltyu/sp1-lightclient-ism
ltyu/verify-ism
ltyu/warp-ism-config
ltyu/zerion-configs
mailbox-branch
mailbox-chainid
main
main-auditv2-merge
main-node-ci
main-to-v3
mattie/512-bit-txoutcomes
mattie/auto-update-prs
mattie/automated-vendoring
mattie/caching-requests
mattie/cosmos-stubs
mattie/finality-blocks-config
mattie/fix-kathy
mattie/inclusive-block-range
mattie/infra-drift-fix
mattie/large-runners
mattie/optional-agent-configuration
mattie/reclaim-funds-from-old-relayer-keys
mattie/relayer-debugging
mattie/sealevel-better-patching
mattie/sealevel-dependency-conflicts-fix
mattie/sealevel/dependencies-part-2
mattie/serejke-fix-1924
mattie/typescript-provider-timeouts
mattie/zkevm-context
merkle-tree-hook-indexer
merkle-vs-mapping
mo/check-avs-cli-command
mo/infra-warp-config-generation
mo/key-funder-debug
mo/keyfunder-707db4a27
mo/non-aw-owned-proxy-checks
mo/verify-proxy-contracts
mo/warp-balance-monitor-validator-names
monitor-war-routes-general
multi-message-relay
multisig-init
nam-rebase
nambrot-patch-1
nambrot/add-gcp-address-to-allconfigs
nambrot/arc-test
nambrot/callforwarder
nambrot/celo-safe
nambrot/chain-connection-to-provider
nambrot/checkpointer-local
nambrot/ci-build
nambrot/circle-relayer
nambrot/core-deploy-fixes
nambrot/debug-fork-ci
nambrot/deploy-aggregation-relayer
nambrot/deploy-helloworld
nambrot/deploy-igp
nambrot/deploy-test-recipient
nambrot/deployment-tooling
nambrot/dev-community
nambrot/dockerignore
nambrot/double-update-script
nambrot/extra-partial-config
nambrot/failed-refactor
nambrot/fix-contract-metrics-avalanche
nambrot/fix-contracts-metrics
nambrot/fix-polygon-updater-old-root
nambrot/foundry-in-ica
nambrot/fundraise-xapp
nambrot/generate-message-with-proof
nambrot/hyp7683
nambrot/igp-deployment-woes
nambrot/in-over-or
nambrot/infra-multiprovider
nambrot/kurtosis-cli
nambrot/loop-with-sleep
nambrot/manual-processing-deploy
nambrot/mintable-token-standard
nambrot/nam-run-feedback
nambrot/optics-ts-interface
nambrot/oracle-updates
nambrot/owner-without-ism
nambrot/parallelize-sol-testing
nambrot/polygon-updater-rotation
nambrot/processor-s3-pusher
nambrot/publish-script
nambrot/relay-specific-message
nambrot/remove-dependabot
nambrot/rename-abacus-solidity-typechain
nambrot/rename-network-to-chain
nambrot/repro-2-2-run-locally
nambrot/resolve-lock
nambrot/rotate-mainnet-etherscan
nambrot/rpc-validator
nambrot/scroll-overrides
nambrot/sdk-0.2.4
nambrot/selective-index-on
nambrot/speed-up-events
nambrot/staging-community-provider
nambrot/static-igp
nambrot/superchain-ism
nambrot/trace-level-s3
nambrot/transfer-owner-no-op
nambrot/try-gas-payment-test-abstraction
nambrot/update-kathy
nambrot/update-optics-provider
nambrot/updater-pause
nambrot/verification-fies
nambrot/watcher-test
nambrot/yo-deploy
nexus-neutron-validators
noah/agg-failure
noah/co
noah/dr-fix
noah/move-safe
noah/no-warp
noah/node-expwarn-cli
noah/prompt
noah/root
noah/warp-ica
noah/zod-2
op-interceptor-deployer
op-stack-hook-deployment
opt-mailbox-delivered
optics-v2
parameterize-infra-paths
pb/chore-test-conditions
pb/duplicate-chainid-support
pb/enable-hyperliquidevmtestnet
pb/sprint32-mainnet
pb/stride-va
pb/submitter-types
pb/test-e2e-breaks
pb/treasure-zklink
pb/turbo
pb/verify-viction
pb/zerion
pb/zksync
pjson-pruning
pr-analytics
processor-fixes
public-main
rc-validators
rebalance-collateral
retry-signer
reverse-ica
revert-964-hacken-critical-1
rossy/cli-version-fix
rossy/codespell-changeset
rossy/multiprovider-no-generic
router-not-upgradeable
router<0.8
routing-interceptor
rpc-fork-cache
schema-fixes
sdk-release
snapshot-igp-config
storage-ism
submodules-1.0.0
submodules-path-2
suppress-coverage-patch
symbiotic
test-recipient-ism-config
test-sol-fixes
test-sol-speed
testnet-dtm
testnet4
testnet4-deployment
tmp-keyfunder
token-testing-forge
transfer-and-call
transient-current-message-id
trevor/1.4.2-beta69
trevor/add-injective-back
trevor/addtl-igp-cmds
trevor/arbitrum-gas-amounts
trevor/bridge-app-interchain-gas-contracts
trevor/conditional-middlewares-suck
trevor/cosmos-cleanup-2
trevor/dao-ism
trevor/debug-verbosity
trevor/debugging-sept-21
trevor/dependency-attempts
trevor/deploy-relayer-funder-multi-context
trevor/deploy-testrecipient-rollup-testnets
trevor/deploy-v2
trevor/deploy-v2-relayer-feb-1-2024
trevor/deploying-ancient8
trevor/deploying-to-zbc-testnet
trevor/disable-rarichain-rpc
trevor/eclipsedevnet-deploy
trevor/env-var-tip
trevor/fallback-igp
trevor/fastusd-infra-checking
trevor/fix-announcement-issues
trevor/fix-e2e-mar-31
trevor/fix-feat/deploy-new-rc
trevor/fix-inaccurate-svm-comment
trevor/fix-polygon-updater-old-root
trevor/fix-processor-priority
trevor/force-readonly-collateral-mints
trevor/gelato-mainnet-abacus
trevor/gelato-testnet2
trevor/grpc-refactor
trevor/hacky-nautilus-indexing-fix-attempt
trevor/helloworld-check-mostly-works
trevor/helloworld-program
trevor/helloworld-program-and-tooling-not-working
trevor/higher-sol-fees
trevor/key-funder-fallbackprovider
trevor/last-agent-release
trevor/legacy-ethers
trevor/local-igp-for-playing-with
trevor/lz-reorg-periods
trevor/mainnet-rc-quorumprovider
trevor/merge-main-jul-6
trevor/merge-v3
trevor/merkle-indexing-as-message
trevor/native-warp-route-allow-donate
trevor/new-featv3-cosmos
trevor/nits-and-no-invariant
trevor/no-address-filter
trevor/no-eip-1559
trevor/on-chain-fee-quoting-calculator
trevor/opentelemetry
trevor/opentelemetry-stackdriver
trevor/oracle-updates-mode-blast-try-batching
trevor/parallel-pod-management-policy
trevor/play-with-ci
trevor/playing-with-validator-announce
trevor/port-over-addtl-igp-cmds
trevor/proteus-from-last-agent-release
trevor/proteus-from-last-agent-release-1
trevor/quick-scroll-moonbeam-fix
trevor/read-txs-nov-8
trevor/relayer-use-gelato-scaffolding
trevor/sealevel-igp
trevor/sei-fix
trevor/send-unblocking-tx
trevor/some-svm-improvements
trevor/suggestion
trevor/svm-collateral-readonly-mint
trevor/test-dispatch-return-value
trevor/try-ethers-quorum-estimate-gas-fix
trevor/try-fix-e2e
trevor/upgrade-registry-update
trevor/use-gas-estimate-components-in-arb
trevor/use-secret-rpc-urls-awk-branch-setup
trevor/wip-transfer-test
trusted-relayer-ism
typechain11
upgradable-warp-routes-rossy
upgrades-v2
v1
v2
v2-2
v2-create2
v3
v3-agents
v3-agents-feedback
v3-agents-rebase
v3-review
validator-correctness
verify-igp
verify-mainnet
verify-new-testnet2
warp-deploy-ism-config
warp-route-v3
webbhorn/gelato-PR-submitter-prep
webbhorn/gelato-tip
webbhorn/gelato-tip-wip
webbhorn/gelato/demo-cli
webbhorn/gelato/op
xeno/better-chain-selection-for-single-chain
xeno/ica-router-management
xeno/split-cli-core-e2e-tests
xeno/update-ism-derivation-for-ica-support
yarn-4.1.0
yorhodes-patch-1
yorhodes/427
yorhodes/429
yorhodes/450
yorhodes/479
yorhodes/inbox-enrollments
zksync
0.2.1
0.2.4
0.3.1
1.0.0-beta5
2023-06-08
@hyperlane-xyz/cli@3.10.0
@hyperlane-xyz/cli@3.11.0
@hyperlane-xyz/cli@3.11.1
@hyperlane-xyz/cli@3.13.0
@hyperlane-xyz/cli@3.13.0-next.0
@hyperlane-xyz/cli@3.14.0
@hyperlane-xyz/cli@3.15.0
@hyperlane-xyz/cli@3.15.1
@hyperlane-xyz/cli@3.16.0
@hyperlane-xyz/cli@3.2.0
@hyperlane-xyz/cli@3.3.0
@hyperlane-xyz/cli@3.4.0
@hyperlane-xyz/cli@3.5.0
@hyperlane-xyz/cli@3.5.1
@hyperlane-xyz/cli@3.6.0
@hyperlane-xyz/cli@3.6.1
@hyperlane-xyz/cli@3.6.2
@hyperlane-xyz/cli@3.7.0
@hyperlane-xyz/cli@3.8.0
@hyperlane-xyz/cli@3.8.1
@hyperlane-xyz/cli@3.8.2
@hyperlane-xyz/cli@3.9.0
@hyperlane-xyz/cli@4.0.0
@hyperlane-xyz/cli@4.0.0-alpha.0
@hyperlane-xyz/cli@4.0.0-alpha.1
@hyperlane-xyz/cli@4.0.0-alpha.2
@hyperlane-xyz/cli@4.0.0-beta
@hyperlane-xyz/cli@4.1.0
@hyperlane-xyz/cli@5.1.0
@hyperlane-xyz/cli@5.1.1
@hyperlane-xyz/cli@5.1.2
@hyperlane-xyz/cli@5.2.0
@hyperlane-xyz/cli@5.2.1
@hyperlane-xyz/cli@5.2.1-beta.0
@hyperlane-xyz/cli@5.3.0
@hyperlane-xyz/cli@5.4.0
@hyperlane-xyz/cli@5.5.0
@hyperlane-xyz/cli@5.6.0
@hyperlane-xyz/cli@5.6.1
@hyperlane-xyz/cli@5.6.2
@hyperlane-xyz/cli@5.7.0
@hyperlane-xyz/cli@6.0.0
@hyperlane-xyz/cli@7.0.0
@hyperlane-xyz/cli@7.1.0
@hyperlane-xyz/cli@7.2.0
@hyperlane-xyz/core@3.1.10
@hyperlane-xyz/core@3.10.0
@hyperlane-xyz/core@3.11.0
@hyperlane-xyz/core@3.11.1
@hyperlane-xyz/core@3.12.0
@hyperlane-xyz/core@3.13.0
@hyperlane-xyz/core@3.13.0-next.0
@hyperlane-xyz/core@3.14.0
@hyperlane-xyz/core@3.15.0
@hyperlane-xyz/core@3.15.1
@hyperlane-xyz/core@3.16.0
@hyperlane-xyz/core@3.2.0
@hyperlane-xyz/core@3.3.0
@hyperlane-xyz/core@3.4.0
@hyperlane-xyz/core@3.5.0
@hyperlane-xyz/core@3.5.1
@hyperlane-xyz/core@3.6.0
@hyperlane-xyz/core@3.6.1
@hyperlane-xyz/core@3.6.2
@hyperlane-xyz/core@3.7.0
@hyperlane-xyz/core@3.8.0
@hyperlane-xyz/core@3.8.1
@hyperlane-xyz/core@3.8.2
@hyperlane-xyz/core@3.9.0
@hyperlane-xyz/core@4.0.0
@hyperlane-xyz/core@4.0.0-alpha.0
@hyperlane-xyz/core@4.0.0-alpha.1
@hyperlane-xyz/core@4.0.0-alpha.2
@hyperlane-xyz/core@4.0.0-beta
@hyperlane-xyz/core@4.1.0
@hyperlane-xyz/core@5.1.0
@hyperlane-xyz/core@5.1.1
@hyperlane-xyz/core@5.1.2
@hyperlane-xyz/core@5.2.0
@hyperlane-xyz/core@5.2.1
@hyperlane-xyz/core@5.2.1-beta.0
@hyperlane-xyz/core@5.3.0
@hyperlane-xyz/core@5.4.0
@hyperlane-xyz/core@5.4.1
@hyperlane-xyz/core@5.5.0
@hyperlane-xyz/core@5.6.0
@hyperlane-xyz/core@5.6.1
@hyperlane-xyz/core@5.7.0
@hyperlane-xyz/core@5.7.1
@hyperlane-xyz/core@5.8.0
@hyperlane-xyz/core@5.8.1
@hyperlane-xyz/core@5.8.2
@hyperlane-xyz/github-proxy@5.2.0
@hyperlane-xyz/github-proxy@5.2.1-beta.0
@hyperlane-xyz/helloworld@3.1.10
@hyperlane-xyz/helloworld@3.10.0
@hyperlane-xyz/helloworld@3.11.0
@hyperlane-xyz/helloworld@3.11.1
@hyperlane-xyz/helloworld@3.12.0
@hyperlane-xyz/helloworld@3.13.0
@hyperlane-xyz/helloworld@3.13.0-next.0
@hyperlane-xyz/helloworld@3.14.0
@hyperlane-xyz/helloworld@3.15.0
@hyperlane-xyz/helloworld@3.15.1
@hyperlane-xyz/helloworld@3.16.0
@hyperlane-xyz/helloworld@3.2.0
@hyperlane-xyz/helloworld@3.3.0
@hyperlane-xyz/helloworld@3.4.0
@hyperlane-xyz/helloworld@3.5.0
@hyperlane-xyz/helloworld@3.5.1
@hyperlane-xyz/helloworld@3.6.0
@hyperlane-xyz/helloworld@3.6.1
@hyperlane-xyz/helloworld@3.6.2
@hyperlane-xyz/helloworld@3.7.0
@hyperlane-xyz/helloworld@3.8.0
@hyperlane-xyz/helloworld@3.8.1
@hyperlane-xyz/helloworld@3.8.2
@hyperlane-xyz/helloworld@3.9.0
@hyperlane-xyz/helloworld@4.0.0
@hyperlane-xyz/helloworld@4.0.0-alpha.0
@hyperlane-xyz/helloworld@4.0.0-alpha.1
@hyperlane-xyz/helloworld@4.0.0-alpha.2
@hyperlane-xyz/helloworld@4.0.0-beta
@hyperlane-xyz/helloworld@4.1.0
@hyperlane-xyz/helloworld@5.1.0
@hyperlane-xyz/helloworld@5.1.1
@hyperlane-xyz/helloworld@5.1.2
@hyperlane-xyz/helloworld@5.2.0
@hyperlane-xyz/helloworld@5.2.1
@hyperlane-xyz/helloworld@5.2.1-beta.0
@hyperlane-xyz/helloworld@5.3.0
@hyperlane-xyz/helloworld@5.4.0
@hyperlane-xyz/helloworld@5.5.0
@hyperlane-xyz/helloworld@5.6.0
@hyperlane-xyz/helloworld@5.6.1
@hyperlane-xyz/helloworld@5.6.2
@hyperlane-xyz/helloworld@5.7.0
@hyperlane-xyz/helloworld@6.0.0
@hyperlane-xyz/helloworld@7.0.0
@hyperlane-xyz/helloworld@7.1.0
@hyperlane-xyz/helloworld@7.2.0
@hyperlane-xyz/sdk@3.1.10
@hyperlane-xyz/sdk@3.10.0
@hyperlane-xyz/sdk@3.11.0
@hyperlane-xyz/sdk@3.11.1
@hyperlane-xyz/sdk@3.12.0
@hyperlane-xyz/sdk@3.13.0
@hyperlane-xyz/sdk@3.13.0-next.0
@hyperlane-xyz/sdk@3.14.0
@hyperlane-xyz/sdk@3.15.0
@hyperlane-xyz/sdk@3.15.1
@hyperlane-xyz/sdk@3.16.0
@hyperlane-xyz/sdk@3.2.0
@hyperlane-xyz/sdk@3.3.0
@hyperlane-xyz/sdk@3.4.0
@hyperlane-xyz/sdk@3.5.0
@hyperlane-xyz/sdk@3.5.1
@hyperlane-xyz/sdk@3.6.0
@hyperlane-xyz/sdk@3.6.1
@hyperlane-xyz/sdk@3.6.2
@hyperlane-xyz/sdk@3.7.0
@hyperlane-xyz/sdk@3.8.0
@hyperlane-xyz/sdk@3.8.1
@hyperlane-xyz/sdk@3.8.2
@hyperlane-xyz/sdk@3.9.0
@hyperlane-xyz/sdk@4.0.0
@hyperlane-xyz/sdk@4.0.0-alpha.0
@hyperlane-xyz/sdk@4.0.0-alpha.1
@hyperlane-xyz/sdk@4.0.0-alpha.2
@hyperlane-xyz/sdk@4.0.0-beta
@hyperlane-xyz/sdk@4.1.0
@hyperlane-xyz/sdk@5.1.0
@hyperlane-xyz/sdk@5.1.1
@hyperlane-xyz/sdk@5.1.2
@hyperlane-xyz/sdk@5.2.0
@hyperlane-xyz/sdk@5.2.1
@hyperlane-xyz/sdk@5.2.1-beta.0
@hyperlane-xyz/sdk@5.3.0
@hyperlane-xyz/sdk@5.4.0
@hyperlane-xyz/sdk@5.5.0
@hyperlane-xyz/sdk@5.6.0
@hyperlane-xyz/sdk@5.6.1
@hyperlane-xyz/sdk@5.6.2
@hyperlane-xyz/sdk@5.7.0
@hyperlane-xyz/sdk@6.0.0
@hyperlane-xyz/sdk@7.0.0
@hyperlane-xyz/sdk@7.1.0
@hyperlane-xyz/sdk@7.2.0
@hyperlane-xyz/utils@3.1.10
@hyperlane-xyz/utils@3.10.0
@hyperlane-xyz/utils@3.11.0
@hyperlane-xyz/utils@3.11.1
@hyperlane-xyz/utils@3.12.0
@hyperlane-xyz/utils@3.13.0
@hyperlane-xyz/utils@3.13.0-next.0
@hyperlane-xyz/utils@3.14.0
@hyperlane-xyz/utils@3.15.0
@hyperlane-xyz/utils@3.15.1
@hyperlane-xyz/utils@3.16.0
@hyperlane-xyz/utils@3.2.0
@hyperlane-xyz/utils@3.3.0
@hyperlane-xyz/utils@3.4.0
@hyperlane-xyz/utils@3.5.0
@hyperlane-xyz/utils@3.5.1
@hyperlane-xyz/utils@3.6.0
@hyperlane-xyz/utils@3.6.1
@hyperlane-xyz/utils@3.6.2
@hyperlane-xyz/utils@3.7.0
@hyperlane-xyz/utils@3.8.0
@hyperlane-xyz/utils@3.8.1
@hyperlane-xyz/utils@3.8.2
@hyperlane-xyz/utils@3.9.0
@hyperlane-xyz/utils@4.0.0
@hyperlane-xyz/utils@4.0.0-alpha.0
@hyperlane-xyz/utils@4.0.0-alpha.1
@hyperlane-xyz/utils@4.0.0-alpha.2
@hyperlane-xyz/utils@4.0.0-beta
@hyperlane-xyz/utils@4.1.0
@hyperlane-xyz/utils@5.1.0
@hyperlane-xyz/utils@5.1.1
@hyperlane-xyz/utils@5.1.2
@hyperlane-xyz/utils@5.2.0
@hyperlane-xyz/utils@5.2.1
@hyperlane-xyz/utils@5.2.1-beta.0
@hyperlane-xyz/utils@5.3.0
@hyperlane-xyz/utils@5.4.0
@hyperlane-xyz/utils@5.5.0
@hyperlane-xyz/utils@5.6.0
@hyperlane-xyz/utils@5.6.1
@hyperlane-xyz/utils@5.6.2
@hyperlane-xyz/utils@5.7.0
@hyperlane-xyz/utils@6.0.0
@hyperlane-xyz/utils@7.0.0
@hyperlane-xyz/utils@7.1.0
@hyperlane-xyz/utils@7.2.0
@hyperlane-xyz/widgets@5.0.0
@hyperlane-xyz/widgets@5.1.0
@hyperlane-xyz/widgets@5.1.1
@hyperlane-xyz/widgets@5.1.2
@hyperlane-xyz/widgets@5.2.0
@hyperlane-xyz/widgets@5.2.1
@hyperlane-xyz/widgets@5.2.1-beta.0
@hyperlane-xyz/widgets@5.3.0
@hyperlane-xyz/widgets@5.4.0
@hyperlane-xyz/widgets@5.5.0
@hyperlane-xyz/widgets@5.6.0
@hyperlane-xyz/widgets@5.6.1
@hyperlane-xyz/widgets@5.6.2
@hyperlane-xyz/widgets@5.7.0
@hyperlane-xyz/widgets@6.0.0
@hyperlane-xyz/widgets@7.0.0
@hyperlane-xyz/widgets@7.1.0
@hyperlane-xyz/widgets@7.2.0
agents-1.0.0
agents-1.0.1
agents-2023-04-14
agents-2023-05-25
agents-2023-05-26
agents-2023-06-08
agents-2023-06-14
agents-2023-07-24
agents-2023-07-25
agents-2023-08-23
agents-2023-11-28
agents-2023-11-29
agents-2023-11-30
agents-2023-12-14
agents-2024-01-29
agents-2024-03-19
agents-2024-03-21
agents-2024-05-30
agents-2024-06-19
agents-v1.0.0
audit-fyeo-responses-0
audit-remediations
audit-scope-0
audit-v2
fyeo-fixes
hacken-fixes
mainnet-contracts
show
testnet2-contracts
testnet3
v.0.2.0
v.1.5.3
v0.0.0-testnet.0
v0.2.0
v0.2.1
v0.2.2
v0.2.3
v0.3.1
v0.4.0
v0.4.1
v0.5.0
v0.5.0-beta0
v0.5.1
v0.5.2
v0.5.3
v0.5.5
v1.0.0
v1.0.0-beta1
v1.0.0-beta5
v1.0.0-beta6
v1.1.0
v1.2.0
v1.2.1
v1.2.2
v1.2.3
v1.3.0
v1.3.1
v1.3.2
v1.3.3
v1.3.4
v1.3.7
v1.4.0
v1.4.1
v1.5.0
v1.5.1
v1.5.8
v2
v3-audit-remediations
v3-solidity
zksyncbeta
${ noResults }
949 Commits (ab28721b6f8d41be65fe2940f5105ee9f1425da2)
Author | SHA1 | Message | Date |
---|---|---|---|
xeno097 |
1ca8574510
|
feat: zero warp deploys (#4876)
### Description Adds infra support for tracking and checking USDC, USDT, cbBTC and ETH routes for zeronetwork ### Drive-by changes - Removed unused imports ### Related issues ### Backward compatibility - Yes ### Testing - Manual ![image](https://github.com/user-attachments/assets/4be51df9-1d95-46cc-8dbb-f2e97f9eb744) ![image](https://github.com/user-attachments/assets/848ba67a-e62e-4c9b-ae64-052d935c86f4) --------- Co-authored-by: Trevor Porter <tkporter4@gmail.com> |
5 days ago |
Paul Balaji |
61157097bc
|
feat: deploy to swell & lumiaprism (#4919)
### Description feat: deploy to swell & lumiaprism ### Drive-by changes parallelise router enrollment in HyperlaneRouterDeployer ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing manual --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com> |
6 days ago |
Trevor Porter |
8f8853bcd7
|
feat: env var to set Jito tip as a stopgap (#4916)
### Description - Intending to follow up with a more legit way of figuring out fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
7 days ago |
Trevor Porter |
ff9e8a72b8
|
feat: track ATA payer balances in warp monitors instead of key funder (#4913)
### Description - We need to track balances of "ATA payer" accounts, which are accounts that have balances that are used to pay for rent for recipients that have never received a particular token before. The balance is in the native token as that's what the SVM uses to charge rent. Previously, we were tracking these in the key funder in a very manual and annoying process. Now, this is tracked automatically when a warp route monitor is set up. - Removed the old logic in the key funder - Consolidated some code to ensure the same gauge is used to track wallet balances throughout TS What I'll do after this is merged: - deploy an updated key funder to no longer track ATA payers - deploy new warp route monitors with this Example of the metric now included in the warp monitor: ``` # HELP hyperlane_wallet_balance Current balance of a wallet for a token # TYPE hyperlane_wallet_balance gauge hyperlane_wallet_balance{chain="eclipsemainnet",wallet_address="CijxTbPs9JZxTUfo8Hmz2imxzHtKnDFD3kZP3RPy34uJ",wallet_name="SOL/eclipsemainnet-solanamainnet/ata-payer",token_symbol="Native",token_name="Native"} 0.039941128 ``` ### Drive-by changes - Some drive-bys to allow you to omit a warp route ID as a CLI arg to some scripts to get an interactive prompt. Found this useful as it's annoying to remember and type out the warp route ID structure ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
7 days ago |
Paul Balaji |
24784af958
|
feat: add GcpValidator using GcpStorageWrapper (#4878)
### Description Introduce GcpValidator for retrieving announcements, checkpoints and metadata for a Validator posting to a GCP bucket. Uses GcpStorageWrapper for bucket operations. ### Drive-by changes update `check-validator-version` to read gcp buckets too ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility yes ### Testing manual before: ``` Error getting metadata for validator 0x14ADB9e3598c395Fe3290f3ba706C3816Aa78F59 on chain flowmainnet: Error: Unable to parse location gs://ff-hyperlane-validator-1/gcsAnnouncementKey │ 18 │ 'flowmainnet' │ '0x14ADB9e3598c395Fe3290f3ba706C3816Aa78F59' │ 'flow foundation' │ 'UNKNOWN' │ ``` after: ``` │ 22 │ 'flowmainnet' │ '0x14ADB9e3598c395Fe3290f3ba706C3816Aa78F59' │ 'flow foundation' │ 'nov-7-batch' │ ``` |
7 days ago |
Paul Balaji |
ef33b5b6b2
|
feat: script to check versions of default validators (#4774)
### Description feat: script to check versions of default validators also prints age of the commit for mismatched validators ### Drive-by changes update s3 validator to return `metadata_latest.json` ### Related issues na ### Backward compatibility ye ### Testing manual --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com> |
7 days ago |
Trevor Porter |
2f77bb0601
|
feat: add Everclear relayer app context (#4912)
### Description Tracks messages from the hub/spoke contracts here https://docs.everclear.org/resources/contracts/mainnet (HubGateway (Everclear hub) <> EverclearSpoke (all other spoke chains)). Went with sender tracking to help us flag if there are other new spokes that pop up ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
7 days ago |
github-actions[bot] |
935747609d
|
Version Packages (#4879)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/cli@7.2.0 ### Minor Changes - d51815760: Support using the CLI to deploy warp routes that involve foreign deployments - 81ab4332f: Remove ismFactoryAddresses from warpConfig - 4b3537470: Changed the type of defaultMultisigConfigs, to track validator aliases in addition to their addresses. ### Patch Changes - Updated dependencies [ |
1 week ago |
Paul Balaji |
4b3537470e
|
feat: add validator operator aliases to default multisig config (#4896)
### Description feat: add validator operator aliases to default multisig config tldr: updated this type and anywhere it's been used ![image](https://github.com/user-attachments/assets/ab055c4f-2fef-4513-a0ff-c574021859c8) - updates `MultisigConfig.validators` type from Address[] to ValidatorConfig[] - `ValidatorConfig` includes both an address + an alias, to be able to track the operator aliases in-code - update any usage of `defaultMultisigConfigs` and `MultisigConfig` type - add `multisigConfigToIsmConfig` helper method to easily convert to `MultisigIsmConfig` format (ie. no aliases) this will simplify the logic in https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4774, and enable us to auto-generate the default ISMs docs page after an SDK update ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing - added extra tests to ensure address/aliases are somewhat sound - `yarn tsx scripts/check/check-validator-announce.ts -e mainnet3` still looks good --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com> |
1 week ago |
J M Rossy |
e32ee592d7
|
chore: Setup Syncpack (#4902)
### Description - Setup Syncpack which can check for package version inconsistencies across the monorepo - Run `yarn syncpack fix-mismatches` to fix existing issues ### Backward compatibility Yes |
1 week ago |
Trevor Porter |
d51815760b
|
feat: deploy apxETH and ezSOL routes (#4901)
### Description Ownership transfer pending getting addresses ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
1 week ago |
Trevor Porter |
43192bd6a9
|
feat: basic Safe transaction decoder (#4800)
### Description Basic functionality to verify multisig txs: - Works with multiple txs from multiple chains (though atm, just 1 tx per chain in the output) - Loudly complains if there's anything unknown - Known scenarios are: - Multicalls - ICA txs - router enrollment - default ISM setting Example usage: ``` yarn tsx ./scripts/safes/parse-txs.ts -e mainnet3 --chains ethereum mantapacific bsc arbitrum optimism base blast linea mode fraxtal taiko sei zircuit --txHashes 0x7f9344cc0b3fa68ece139fb9f0d2cf854c983c343a7680c6ab7b4bfb3924c188 0x1e8e00b7375085a3e3579659815611d1e8240aa43c8826d05347a3066603330d 0x39324715341f856466ca2764468bc31c3f057c8191c99ddad284714730f9337b 0x54eeae0cf702f6a9a3929712e196bb51e0d34778f5948ae8562e4456bb649c14 0x425d8fd82fb390a91f170c32a3bb8839dc9182ad9634111d477af85320d04612 0xbd29fe0f7387ac06bea2049eb26fb9c7b62ed4e412f84137de2a94fe917adca3 0xf6f05f757c22af8a306545d20238ecf3326e93d12aaeecf64d1527daa20c1ec6 0xd9bc3cf2f7ab01560fc99e57c25113d07283245554c4c133f8aa501fb0c21147 0xc6ed50e5ccdd001022f953ae31d7f0bbf88af78bc3dae593b62ad11725cfc900 0xb703be9d342b126f7596ce5431f5ead2192a95c92df9f3c1b76f5242ce8bba4f 0x662b126f552cdc5fcdc9fdad382e28c249a511786e0056dca2bb75ac452878a3 0x246e805047ece2522d98c6841cebf7ad1ce83b4503533a77d73e1b4324ea3ce8 0x412f787db9abdc9d4d4cf863b514790b7e57d5c1e2d9a963018c8b9a3a523fb9 ``` Definitely messy and intended to be the basis of better tooling in the future. ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com> |
1 week ago |
Paul Balaji |
a94b1600f3
|
feat: deploy to B² Network (#4894)
### Description feat: deploy to B² Network ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing manual --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com> |
1 week ago |
Trevor Porter |
3f013d1d8d
|
chore: transfer ownership for cbBTC warp deploy on Flow <> Ethereum (#4893)
### Description - Transfers ownership of the cbBTC warp route between flow and ethereum - A fix to ensure that proxy admin ownership is set ### Drive-by changes - a driveby to prevent rebuilding the multiprovider tons of times in the check warp deploy script ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
1 week ago |
Paul Balaji |
111e241532
|
feat: nov 21 deploy batch (#4885)
### Description Deploy new core chains: boba, duckchain, superseed, unichain, vana. ### Drive-by changes igp updates ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing manual --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com> |
2 weeks ago |
Trevor Porter | 115486e2bd |
feat: ensure consistent decimals in Token checker
|
2 weeks ago |
Trevor Porter |
58425a2de3
|
feat: add Flow <> Ethereum cbBTC warp route to infra, mild refactor to warp config getters (#4868)
### Description - Includes the Flow cbBTC warp route getter (https://github.com/hyperlane-xyz/hyperlane-registry/pull/380) - Includes the ownership transfer for the weETHs warp route - Forces config getters to be more explicit about ownership by having the router config no longer implicitly set owner configs. See https://discord.com/channels/935678348330434570/1306554055895683113 for some context. Now you need to explicitly opt into transferring ownership to our colder setup ### Drive-by changes - Removes a bunch of ts-ignores that aren't needed in the config getters ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
2 weeks ago |
Paul Balaji |
979bceb660
|
feat: script to print and execute pending safe txs (#4704)
### Description feat: script to print and optionally execute pending safe txs ### Drive-by changes add optional chain selection array to `withChains` and `withChainsRequired` ### Related issues na ### Backward compatibility yes ### Testing Example without execution: ![image](https://github.com/user-attachments/assets/2bac68c6-e8fe-4aec-a005-f255259658da) Example with execution: ![image](https://github.com/user-attachments/assets/6a1729d5-a17d-4e33-b7c9-b1b02bc07073) ![image](https://github.com/user-attachments/assets/80ab11bb-fbf9-4409-97f8-34899d057e16) --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com> |
2 weeks ago |
Lee |
3ce70725ee
|
chore: Revert "feat: Add Zerion config generator (#4870)" (#4880)
This reverts commit
|
2 weeks ago |
Lee |
250853eff4
|
feat: Add Zerion config generator (#4870)
### Description Adds Zero config generators for USDB, WBTC, BNB, Pol ### Drive-by changes - Conditional for address zero check ### Backward compatibility Yes ### Testing Manual |
2 weeks ago |
github-actions[bot] |
23a2679bbe
|
Version Packages (#4848)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/cli@7.1.0 ### Minor Changes - 5db46bd31: Implements persistent relayer for use in CLI ### Patch Changes - Updated dependencies [ |
2 weeks ago |
Trevor Porter |
9ca2333bf0
|
feat: more app contexts (#4874)
### Description - Adds the endurance USDC warp deploy so it's a relayer app context - Adds Velodrome contracts, contracts were found from their private fork / in tg with them https://github.com/velodrome-finance/superchain-contracts-private/tree/main/deployment-addresses - Adds Aave contracts, contracts were found by poking around https://app.aave.com/governance/v3/proposal/?proposalId=92, which led to https://github.com/bgd-labs/aave-delivery-infrastructure?tab=readme-ov-file#deployed-addresses and seeing which contracts were sending/receiving messages in our explorer. They don't have a typical router setup -- some messaging is unidirectional. The sending address is more static than the receiving address, so I've set the matching list to be based off the sender to make configuration simpler. https://github.com/bgd-labs/aave-delivery-infrastructure?tab=readme-ov-file#deployed-addresses is the source of truth for these addresses ### Drive-by changes - Forces a warp ID to be picked in the warp monitor flow ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
2 weeks ago |
Trevor Porter |
85dc14d827
|
feat: script for getting key material (#4829)
### Description Corresponding info on how to use this efficiently, PSA will follow https://www.notion.so/hyperlanexyz/Runbook-83c755f2652943289cf98cd1309487a8?pvs=4#1366d35200d68056b827e9e6115f3ea2 - Prints the private key in a subshell but not in a normal tty - Intended to encourage healthier key habits that don't write keys to the filesystem, as described in the first step of https://discord.com/channels/935678348330434570/1296491706417549413/1301158531667595265 ### Drive-by changes - groups some key related scripts ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
2 weeks ago |
J M Rossy |
0cd65c5715
|
chore: Migrate various wallet hooks from the Warp UI to the Widgets lib (#4865)
### Description More ground-work for the upcoming Warp Deploy app No new code, just migrating things from the Warp UI Corresponds with https://github.com/hyperlane-xyz/hyperlane-warp-ui-template/pull/326 Fixes https://github.com/hyperlane-xyz/hyperlane-warp-ui-template/issues/321 ### Drive-by changes Update the hyp registry versions to 6.1.0 ### Backward compatibility Yes ### Testing Tested in Warp UI and storybook <img width="1000" alt="Screenshot 2024-11-16 at 7 08 00 PM" src="https://github.com/user-attachments/assets/f8f9c616-01c4-46e1-8b3b-98415741d4e0"> |
2 weeks ago |
Trevor Porter |
515980e627
|
chore: recent relayer deploy (#4867)
### Description - Deployed the relayer to include https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4858 ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
2 weeks ago |
Yorke Rhodes |
5db46bd315
|
feat: persistent ts relayer (#4831)
### Description - Adjust long running TS relayer with retry queue instead of crashing. - Adds a "whitelist" for relaying to specific message senders/recipients. - Adds a "symbol" flag borrowed from warp commands for filtering on a specific warp route. ### Drive-by changes None ### Related issues - Enables warp route deployer to run the CLI relayer in the background and test/share the warp UI. ### Backward compatibility Yes ### Testing CLI e2e tests |
3 weeks ago |
Trevor Porter |
f76984baa5
|
fix: update warp monitors with latest registry to fix collateral value (#4849)
### Description - To include some fixes to the coinGeckoIds of warp routes recently merged into the registry ### Drive-by changes - made an agent metrics log `warn`, which helped debugging some recent issues - Update the eclipsemainnet owner in owners.ts, a mostly symbolic change as this isn't actually used in our tooling in infra ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
3 weeks ago |
Paul Balaji |
1159e0f4ba
|
feat: nov 8 enrollments (#4841)
### Description - enroll new validators for alephzeroevmmainnet, chilizmainnet, flowmainnet, immutablezkevmmainnet, metal, polynomialfi, rarichain, rootstockmainnet, superpositionmainnet, flame, prom - update validators for inevm - update ownership for recent two deploy batches - ICAs re-enabled - zeronetwork safe configured ### Drive-by changes - igp updates - fix some infra helper scripts - skip all chains to skip for ICA - only skip lumia for validator announce check ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing manual + infra helper scripts |
3 weeks ago |
Trevor Porter |
e1c6eef8ab
|
feat: relayer app contexts use warp route artifacts from the registry (#4845)
### Description This PR aims to solve 2 problems: forgetting to add warp routes as app contexts in the relayer, and deduplicating artifacts that live in infra and the registry - Removes a bunch of the duplicated warp route artifacts in infra, in favor of getting them from the registry - Now all WarpRouteIds defined in infra will be auto-populated into the mainnet3 relayers as app contexts, with the label as the warp route ID - This significantly increased the size of the metric app context configuration, which was previously supplied as an env var to the relayers. This caused the env var size limit to be hit. As a workaround, larger configuration strings are now moved into a configmap that will be read in as a JSON by the relayer. I intentionally kept some of the configs as env vars, e.g. the relayChains, because this is much more ergonomic to change on the fly and many of us have operational muscle memory around this that I didn't want to break. - Note one consequence of this is that merkly's ETH app is prone to running out of ETH and causing prep queues to rise. Because of this, I'll ignore merkly eth from our high urgency alert ### Drive-by changes - There are a few places we were whitelisting warp routes in the gas config that I've now removed. From what I can tell none of these are necessary anymore as they were intended to be temporary workarounds. - Updated the addresses for merkly from here https://minter.merkly.com/hyperlane/docs ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
3 weeks ago |
Trevor Porter |
9fcd592878
|
feat: refactor warp monitor to use WarpCore config (#4835)
### Description - Removes the warp monitor specific config format and all the handcrafted yamls from infra - Massive refactor to warp monitor to accommodate this -- tried to make it a bit easier to work work by splitting it into a few files. The changes are generally backward compatible with some small exceptions, like now the metrics use the `TokenStandard` instead of `TokenType` (the former is present in the warp core config, the latter isn't, and there's no way atm to map from the former to the latter) - The warp monitor now takes in a warp ID and gets its config from the registry (recall this is the registry version defined in `.registryrc` if running in the monorepo image) - Deploying the warp monitor now lets you do many at a time and select the ones to deploy interactively. This makes it a bit easier to work with the warp IDs - The names of the warp deploys are based on the warp IDs. Because warp IDs can change as new chains are added, this may cause issues in the future - we'll just need to be cautious of removing the old release to avoid accidentally having 2 of them. For now I think this is fine. The helm release names are also capped at 53 chars so they needed to be truncated - Some changes to the SDK to get the necessary data here. Happy to pull some of these into the warp monitor if people feel they're inappropriate for the SDK (like the `getBridgedSupply`) - Added a test to make sure any warp route IDs in infra are found in the registry - Corresponding PR to the registry here https://github.com/hyperlane-xyz/hyperlane-registry/pull/370 ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
4 weeks ago |
github-actions[bot] |
0754d6218c
|
Version Packages (#4830)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/sdk@7.0.0 ### Major Changes - f48cf8766: Upgrade Viem to 2.2 and Solana Web3 to 1.9 Rename `chainMetadataToWagmiChain` to `chainMetadataToViemChain` - 5f41b1134: Remove getCoingeckoTokenPrices (use CoinGeckoTokenPriceGetter instead) ### Minor Changes - bbb970a44: Redeploy to alephzeroevmmainnet, chilizmainnet, flowmainnet, immutablezkevmmainnet, metal, polynomialfi, rarichain, rootstockmainnet, superpositionmainnet. Deploy to flame, prom. - fa424826c: Add support for updating the mailbox proxy admin owner - 40d59a2f4: Deploy to abstracttestnet and treasuretopaz - 0264f709e: Deploy to alephzeroevmtestnet, update deployment for arcadiatestnet2. - 836060240: Add storage based multisig ISM types - f24835438: Added coinGeckoId as an optional property of the TokenConfigSchema ### Patch Changes - ba0122279: feat: use message context in hook reader IGP derivation - Updated dependencies [ |
4 weeks ago |
xeno097 |
fa424826c0
|
feat: core deploy apply admin proxy ownership fixes (#4767)
### Description This PR updates the `hyperlane core init`, `hyperlane core deploy` and `hyperlane core apply` commands to allow a user to change ownership of the mailbox ProxyAdmin contract by setting a value in the config. ### Drive-by changes - deduped `randomAddress` test util implementations across the `sdk`, 'infra' and `cli` package - added `anvil1` to the `run-e2e-test.sh` script to test `hyperlane core` commands in isolation - implemented the `proxyAdminOwnershipUpdateTxs` to deduplicate proxy admin ownership tx data generation ### Related issues - Fixes #4728 ### Backward compatibility - Yes ### Testing - Manual - e2e ### NOTE: - Merge https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4726 first --------- Co-authored-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com> |
4 weeks ago |
J M Rossy |
5f41b11346
|
fix: Remove coingecko-api-v3 library and de-dupe fetching utils (#4837)
### Description - Remove coingecko-api-v3 lib which is unnecessary and breaks bundling - Remove `getCoingeckoTokenPrices` function which is redundant with `CoinGeckoTokenPriceGetter` - Simplify `CoinGeckoTokenPriceGetter` and remove need for Mock class Related: https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4787 See discussion here: https://discord.com/channels/935678348330434570/1304125818817220653 ### Drive-by changes - Fix bundling issue with Storybook in widgets lib ### Backward compatibility No ### Testing Rewrote unit tests and tested Storybook |
4 weeks ago |
Paul Balaji |
40d59a2f47
|
feat: deploy to abstracttestnet, treasuretopaz (#4839)
### Description - deploy to abstracttestnet, treasuretopaz - standard deployments from this branch - zksync deployments themselves done from https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4761 ### Drive-by changes - testnet igp - fix validator announce script, should only be skipping `lumia` ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing manual --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com> |
4 weeks ago |
Paul Balaji |
bbb970a442
|
feat: nov 6 chain deploy batch (#4833)
### Description - redeploy to alephzeroevmmainnet chilizmainnet flowmainnet immutablezkevmmainnet metal polynomialfi rarichain rootstockmainnet superpositionmainnet - deploy to flame prom ### Drive-by changes - igp updates ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing manual --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com> |
4 weeks ago |
Mohammed Hussan |
884b00c5bc
|
feat(warpMonitor): Update warp monitor image tag (#4825)
### Description - Update warp monitor image tag |
4 weeks ago |
J M Rossy |
f48cf87667
|
chore: Upgrade Viem and Solana Web3 (#4821)
### Description - Breaking change: Upgrade Viem from 1.x to 2.2 - Upgrade Solana Web3 to 1.9 - Upgrade Solana SPL Token to 0.4.9 ### Related issues Required for https://github.com/hyperlane-xyz/hyperlane-warp-ui-template/issues/173 ### Backward compatibility No ### Testing Tested EVM and Solana wallet connections and transfers in the Warp UI. See https://github.com/hyperlane-xyz/hyperlane-warp-ui-template/pull/315 |
4 weeks ago |
Paul Balaji |
0264f709e4
|
feat: deploy to arcadiatestnet, alephzeroevmtestnet, inksepolia (#4827)
### Description feat: deploy to arcadiatestnet, alephzeroevmtestnet, inksepolia ### Drive-by changes - update agent configs ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing manual --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com> |
4 weeks ago |
Trevor Porter |
e6f9d5c4fd
|
feat: add weETHs warp route, some drive-by cleanup (#4826)
### Description - Deploys weETHs between Ethereum and Eclipsemainnet - Removes all the warp route generation scripts in favor of a single one - Renames some things throughout infra to be closer to the canonical warp IDs (e.g. add all chain names, sort them, etc) - Removes a bunch of now unnecessary ts-ignores - Moves toward using router configs for non-EVM chains in the warp configs Waiting to merge https://github.com/hyperlane-xyz/hyperlane-registry/pull/362 before updating the registryrc in here so the warp config checker works ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
4 weeks ago |
github-actions[bot] |
f0e8f74087
|
Version Packages (#4816)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/cli@6.0.0 ### Major Changes - e3b97c455: Detangle assumption that chainId == domainId for EVM chains. Domain IDs and Chain Names are still unique, but chainId is no longer guaranteed to be a unique identifier. Domain ID is no longer an optional field and is now required for all chain metadata. ### Patch Changes - Updated dependencies [ |
4 weeks ago |
Paul Balaji |
e3b97c4555
|
feat: detangle chainId / domainId EVM assumptions (#4798)
### Description Detangle assumption that chainId == domainId for EVM chains. - required to support new domain IDs for sept26 chain deploy batch https://github.com/hyperlane-xyz/hyperlane-registry/pull/352 Domain IDs and Chain Names are still unique, but chainId is no longer guaranteed to be a unique identifier. - required to support shadow lumia (current deployment) + prod lumia (new deployment with different domain id) Touches: - evm core/ism/hook/warp modules - multiprovider + chain metadata manager - safe service - renaming `ChainNameOrId` to `ChainNameOrDomain` (where bulk of the diff comes from) ### Drive-by changes - ~~add name of a `chain` to `Annotated` types, since chain ID on a populated transaction is a looser tie to a chain than `domainId` or `chain`~~ - ~~simplify multiprovider.sendtransaction, since `chain` is provided with the annotated transaction~~ - ensure domainId is not optional in the chain metadata schema - requires registry fix https://github.com/hyperlane-xyz/hyperlane-registry/pull/357 - update ethers v5 json rpc submitter to require a `chain` as well ### Related issues - mostly redoes work from https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4599 - will have to be rechecked after zksync changes are also in ### Backward compatibility no ### Testing ci, manual --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com> |
4 weeks ago |
Daniel Savu |
1574a3f2b4
|
chore: update relayer image (#4815)
### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
4 weeks ago |
Mohammed Hussan |
7b3b07900c
|
feat(warpMonitor): Use coingecko api key for value monitoring (#4787)
### Description - Fetching coingecko api from GCP secrets and suing with CoinGecko Client - Using coingecko-api-v3 package to support passing API keys ### Drive-By Changes - Rename eclipse warp route config files and add `tokenCoinGeckoId` ### Testing Manual |
4 weeks ago |
github-actions[bot] |
0772863025
|
Version Packages (#4770)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/core@5.7.0 ### Minor Changes - 469f2f340: Checking for sufficient fees in `AbstractMessageIdAuthHook` and refund surplus - f26453ee5: Added msg.value to preverifyMessage to commit it as part of external hook payload - 0640f837c: disabled the ICARouter's ability to change hook given that the user doesn't expect the hook to change after they deploy their ICA account. Hook is not part of the derivation like ism on the destination chain and hence, cannot be configured custom by the user. - a82b4b4cb: Made processInboundMessage payable to send value via mailbox.process ### Patch Changes - Updated dependencies [ |
4 weeks ago |
Trevor Porter |
fbce40f891
|
fix: warp route checker (#4810)
### Description - Updates the .registryrc, which we will need to update when we add new warp route configs to infra, otherwise we'll get ``` Checking warp route WBTC/eclipsemainnet-ethereum... Error checking warp route USDT/eclipsemainnet-ethereum-solanamainnet: Error: Warp route config for USDT/eclipsemainnet-ethereum-solanamainnet not found in registry Error checking warp route WBTC/eclipsemainnet-ethereum: Error: Warp route config for WBTC/eclipsemainnet-ethereum not found in registry Failed to check warp routes: USDT/eclipsemainnet-ethereum-solanamainnet, WBTC/eclipsemainnet-ethereum ``` - Uses the `Always` imagePullPolicy (https://kubernetes.io/docs/concepts/containers/images/#image-pull-policy) to ensure we always use latest main - A consequence of removing Lumia addresses from the registry in https://github.com/hyperlane-xyz/hyperlane-registry/pull/348 is that this broke checking of the Lumia warp route. I manually specify the required addresses here now. - Also needed to explicitly specify the proxyAdmin ownership Definitely some opportunities for improvement with the warp route deploy flow ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
1 month ago |
Daniel Savu |
ffbc13cc58
|
chore: instantiate router config in warp generators (#4807)
### Description Uncomments generator code to actually instantiate a `routerConfig`, as recommended in https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4799#discussion_r1826157666 ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: Trevor Porter <tkporter4@gmail.com> |
1 month ago |
Trevor Porter |
6dd7fc6211
|
chore: deploy new relayer (#4805)
### Description Deployed a new relayer to get access to #4693 ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> |
1 month ago |
Daniel Savu |
2f0495914a
|
feat: eclipse warp batch #2 (#4799)
### Description - ORCA (eclipse <> solana) - WBTC (ethereum <> eclipse) - USDT (ethereum <> eclipse <> solana) |
1 month ago |
Paul Balaji |
db91968372
|
feat: oct 30 enrollments (#4785)
### Description - update validators for op, mode, lisk as part of superlane - add merkly/mitosis validators for apechain, arbitrumnova, b3, fantom, gravity, harmony, kaia, morph, orderly, snaxchain, zeronetwork, zksync - add blockhunters to default set on redstone, cheesechain ### Drive-by changes - igp updates - introduce `chainsToSkip` list to reuse in deploy.ts and check-deploy.ts - filter out `chainsToSkip` in deploy.ts and check-deploy.ts - add retry logic when doing safe api operations in app governor - update scripts for checking/getting ICAs ### Related issues na ### Backward compatibility yes ### Testing manual --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com> |
1 month ago |
Danil Nemirovsky |
fa06690914
|
feat: Upgrade Scraper so that it stores input data for Ethereum transactions (#4796)
### Description Upgrade Scraper so that it stores input data for Ethereum transactions ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4778 ### Backward compatibility Yes ### Testing Manual run of Scraper with local database Manual run of Scraper with db restored from production backup Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com> |
1 month ago |