
As part of our ongoing effort to ensure the right incentives are in place for verifiers and to direct Axelar’s resources toward the ecosystems delivering the most value, we are proposing a governance vote to discontinue three Amplifier chain integrations: Flow, Berachain, and Plume.
Common Prefix’s 2026 roadmap for Axelar has been centered on institutional adoption, strengthening economic security, enabling compliant and privacy-aware infrastructure, and building institutional products up the stack.
A central part of this has been strengthening economic security and improving verifier and broader ecosystem incentives, as well as focusing the network on ecosystems where real activity exists, where interoperability creates tangible value, and where security assumptions are aligned with Axelar’s long-term standards.
That direction requires a disciplined approach to network expansion: doubling down on key ecosystems we have high conviction on and that we believe are here for the long run, while winding down connections whose cost, associated security risks, and operational overhead are no longer justified.
Every chain connection introduces operational, economic, and security considerations. Flow, Berachain, and Plume were integrated into Axelar through the Amplifier framework and, since launch, have not generated meaningful transaction volume or sustained usage. At the same time, each one requires ongoing verifier infrastructure, which carries real operational costs and dilutes focus across the network.
The foundation has been subsidizing verifier costs across these three connections, amounting to hundreds of thousands of dollars per year. An internal review of interchain transfer activity across these integrations found effectively no sustained economic activity. While some legitimate assets had been registered on these chains, little to no transfer activity was identified across the connections.
This proposal will go through Axelar’s standard governance process. Token holders will have the opportunity to review the full proposal and cast their votes within three days.
We have already been in direct communication with the teams behind all three chains ahead of this proposal going public. If this governance proposal passes, a one-week notice period will begin before the integrations are formally discontinued.
Given the lack of meaningful transfer activity across these connections, we do not expect material impact to users, asset holders, or application developers.
We encourage the community to carefully review this proposal and cast their vote.
Find the governance proposal here.