Skip to content

chore(infra): spin down vana agents (ENG-4333) - #9205

Open
haggis-hyperlane wants to merge 1 commit into
mainfrom
haggis/eng-4333-spin-down-vana-agents
Open

chore(infra): spin down vana agents (ENG-4333)#9205
haggis-hyperlane wants to merge 1 commit into
mainfrom
haggis/eng-4333-spin-down-vana-agents

Conversation

@haggis-hyperlane

Copy link
Copy Markdown
Contributor

Summary

  • Disable relayer/validator/scraper for vana in mainnet3 agent.ts (set false in all three role blocks).
  • Remove the vana entry from aw-validators/hyperlane.json so the validator stops deploying.
  • Chain key remains defined (false), so config validation still passes; no agent-config JSON regen needed (that JSON is built from environmentChainNames, not per-role flags).

Part of the Vana paid-chain deprecation (ENG-4333), contract-end date 2026-08-06. Companion registry PR marks vana deprecated: hyperlane-xyz/hyperlane-registry#1642.

Context

  • Transfer target 0xDDF71a6ddf3FCABBbA4D607b57f0f6Fc0265bb84 verified as a Gnosis Safe v1.4.1 (3/7) on Vana; the two warp routers are already owned by it.
  • Vana core contracts (mailbox 0x3a46…775E, proxyAdmin 0x2f2a…85A7) are still owned by the AW deployer 0x486815…E433 — ownership transfer to the multisig is a separate step.

Follow-ups (not in this PR)

  • Full config removal (balances JSONs, validators.ts, rust mainnet_config.json, SDK multisig defaults, .registryrc bump, etc.) — the heavyweight chore: remove … batch, done once agents are confirmed down.
  • Core-contract ownership transfer to the customer multisig.

Test plan

  • Pre-commit hooks green (lint/format/typecheck)
  • After next mainnet3 agent deploy, confirm vana relayer/validator/scraper no longer deploy

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.

@paulbalaji paulbalaji left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread typescript/infra/config/environments/mainnet3/agent.ts
@paulbalaji

Copy link
Copy Markdown
Collaborator

Rollout ownership update: live cluster state has vana-validator deployed in both mainnet3 (legacy release) and validator-mainnet3 (migrated release). After this merges I will uninstall both; removing only the migrated release would leave the legacy validator signing. I will then redeploy only the Hyperlane relayer/scraper and verify Vana is absent from their running configs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Review

Development

Successfully merging this pull request may close these issues.

2 participants