chore(infra): spin down vana agents (ENG-4333) - #9205
Open
haggis-hyperlane wants to merge 1 commit into
Open
Conversation
Disable relayer/validator/scraper for vana in mainnet3 and remove its aw-validator set, as part of the Vana paid-chain deprecation. Chain key remains defined (set false) so validation still passes.
haggis-hyperlane
requested review from
Mo-Hussain,
paulbalaji and
tkporter
as code owners
August 6, 2026 17:59
paulbalaji
approved these changes
Aug 6, 2026
paulbalaji
left a comment
Collaborator
There was a problem hiding this comment.
Reviewed at 8f9ff1d4355aa23c47bb1748899b17600ce4dc65. Approved: all three role maps exclude Vana, the AW validator artifact is removed, and focused agent-config validation/typecheck/lint/format pass. One required rollout step is noted inline.
Collaborator
|
Rollout ownership update: live cluster state has |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
vanain mainnet3agent.ts(setfalsein all three role blocks).vanaentry fromaw-validators/hyperlane.jsonso the validator stops deploying.false), so config validation still passes; no agent-config JSON regen needed (that JSON is built fromenvironmentChainNames, not per-role flags).Part of the Vana paid-chain deprecation (ENG-4333), contract-end date 2026-08-06. Companion registry PR marks
vanadeprecated: hyperlane-xyz/hyperlane-registry#1642.Context
0xDDF71a6ddf3FCABBbA4D607b57f0f6Fc0265bb84verified as a Gnosis Safe v1.4.1 (3/7) on Vana; the two warp routers are already owned by it.0x3a46…775E, proxyAdmin0x2f2a…85A7) are still owned by the AW deployer0x486815…E433— ownership transfer to the multisig is a separate step.Follow-ups (not in this PR)
validators.ts, rustmainnet_config.json, SDK multisig defaults,.registryrcbump, etc.) — the heavyweightchore: remove …batch, done once agents are confirmed down.Test plan