# Axelar deactivates routing for the legacy Centrifuge chain

> Axelar stopped routing transfers and messages to and from the deprecated legacy Centrifuge chain.

- URL: https://riadefi.com/on-chain/2026-06-06-axelar-centrifuge-legacy-chain-route-deactivation-proposal-473/
- Type: Closure or deprecation
- Stage: Deprecated
- Evidence: confirmed
- Materiality: watch
- Event date: 2026-06-06
- Version: 1, published 2026-08-22 (first published 2026-08-22)
- Advisor-relevant: yes
- Affects: Axelar (protocol)

## What happened

Axelar governance passed proposal 473 and deactivated the legacy Centrifuge chain in the nexus module.

## What changed

Axelar stopped routing transfers and messages to and from the deprecated legacy Centrifuge chain.

## What did not change

The proposal did not deactivate other Axelar integrations or affect Centrifuge's newer Ethereum-native CFG token directly.

## Confirmed

- Proposal 473 passed on June 6.
- The payload is an Axelar DeactivateChainRequest naming centrifuge.
- The stated migration window for the legacy canonical token had closed on November 30, 2025.
- The proposal states that the legacy chain remained block-producing but was no longer actively supported.

## Still open

- Any residual user balances, unsupported messages, or applications still relying on the retired route are not identified by the record.

## What it means for an advisor

- Remove the legacy Centrifuge route from any approved Axelar path inventory.
- Confirm that no client workflow or dependency still references the deprecated integration.
- Preserve the distinction between this route retirement and the status of Ethereum-native CFG.

## Sources

1. [Deactivate legacy EVM chain centrifuge](https://axelarscan.io/proposal/473) · Axelar on-chain governance · 2026-06-06


---

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