Axelar governance executes Moonbeam connection deactivation

What happened

Axelar governance proposal 494 passed and executed a Nexus DeactivateChainRequest for Moonbeam. Axelar's Nexus state reports the Moonbeam connection as inactive.

What changed

Moonbeam is no longer an active Axelar Nexus connection, removing that route from Axelar's available cross-chain perimeter until a separate reactivation action occurs.

What did not change

The event did not establish an exploit of Axelar's validator consensus, threshold-signature, or gateway-contract layer. Other Axelar connections and the protocol's consensus thresholds were not changed by this proposal.

Confirmed

• Proposal 494 was submitted and began voting on August 1, 2026.
• Voting ended on August 4 with proposal status PASSED, 157,176,988,734,355 yes units, and no negative votes.
• The proposal message was an Axelar Nexus DeactivateChainRequest naming Moonbeam.
• The proposal record contains no failed execution reason.
• Axelar Nexus state reports Moonbeam activated=false.

Still open

• The operational reason for the deactivation is not stated in the proposal metadata.
• The treatment of in-flight transfers and any user-facing recovery process was not specified.
• No reactivation conditions or timetable were supplied.

What it means for an advisor

• Remove Moonbeam as an assumed available Axelar route in dependency and exit-planning maps.
• Identify any approved or client-held position whose entry, exit, or recovery path depended on Axelar's Moonbeam connection.
• Review integration-specific continuity controls; Axelar approval does not certify that an affected downstream route remains usable.