Axelar approves the v1.2.1 fee-burn upgrade

What happened

Axelar governance passed proposal 284 to upgrade Axelar Core to v1.2.1 at the specified upgrade height.

What changed

The approved software changes transaction-fee allocation so the community-tax portion remains in the community pool and the remainder is burned instead of distributed to token holders.

What did not change

The retained primary evidence does not independently establish historical execution at the specified height. It does not show a change to gateway signing thresholds, validator custody, supported-chain security assumptions, or Ketju approval status, and it does not establish that the upgrade made Axelar safer.

Confirmed

• Axelar on-chain proposal 284 passed and specifies the v1.2 upgrade at height 16837700.
• The proposal states that AXL transaction fees will be sent to a burn address instead of distributed to token holders.
• The official release identifies migration, distribution, dependency, and burner-permission changes included in v1.2.1.

Still open

• The retained evidence does not independently confirm that historical height 16837700 executed successfully.
• Any effect of the new fee flow on validator incentives and dependency resilience requires memo review.

What it means for an advisor

• Review the Axelar memo's economic-security and validator-incentive assumptions against the new fee allocation.
• Record v1.2.1 as the operative core version for dependency diligence; do not infer a custody or bridge-security improvement from the upgrade alone.