# Axelar executes VotingVerifier migrations across ten Amplifier chains

> The VotingVerifier implementation governing verification for the ten named integrations moved to code ID 64, with chain-codec addresses supplied in each migration message.

- URL: https://riadefi.com/on-chain/2026-05-22-axelar-voting-verifier-code64-ten-chain-migration/
- Type: Upgrade or migration
- Stage: Executed
- Evidence: confirmed
- Materiality: material
- Event date: 2026-05-22
- Version: 1, published 2026-08-22 (first published 2026-08-22)
- Advisor-relevant: no
- Affects: Axelar (protocol)

## What happened

Axelar governance passed and executed proposal 472, migrating ten VotingVerifier contracts to code ID 64 across Flow, Sui, Stellar, XRPL EVM, Plume, Hedera, Berachain, Hyperliquid, Monad, and Solana Amplifier integrations.

## What changed

The VotingVerifier implementation governing verification for the ten named integrations moved to code ID 64, with chain-codec addresses supplied in each migration message.

## What did not change

The record did not establish any change to Axelar's validator consensus quorum, gateway contracts, emergency committee, or integrations outside the ten named Amplifier chains.

## Confirmed

- Proposal 472 reached passed status on May 22, 2026.
- The proposal contained ten MsgMigrateContract messages.
- Each migration targeted VotingVerifier code ID 64.
- The named integrations were Flow, Sui, Stellar, XRPL EVM, Plume, Hedera, Berachain, Hyperliquid, Monad, and Solana.
- Live contract information for sampled proposal targets reports code ID 64.

## Still open

- The behavioral and security differences between the prior VotingVerifier implementation and code ID 64.
- The audit coverage and deployment testing for the new implementation and chain-codec dependencies.
- Whether all ten integrations processed messages normally after migration.
- Whether any Ketju position used one of the named Amplifier routes.

## What it means for an advisor

- Review Axelar's integration-specific verification assumptions for any contemplated route among the ten migrated chains.
- Obtain the code diff, audit, and post-migration operating evidence before treating the upgrade as risk-reducing.
- No exploit or consensus-threshold change is established, so the event requires review rather than an automatic restriction.

## Sources

1. [Migrate VotingVerifier to code id 64 on 10 chains](https://axelarscan.io/proposal/472) · Axelar on-chain governance · 2026-05-22


---

Published by Ketju Research on RIADeFi (https://riadefi.com). Educational research for financial professionals; not investment, legal, tax, or compliance advice.