Deep Dive
1. Core Protocol Active Development (3 September 2026)
Overview: The primary Axelar network application, axelar-core, shows consistent development activity. A commit was made to the main branch on 3 September 2026, reflecting ongoing work on the node software that validators run.
The repository has 54 contributors and has seen over 1,500 commits, signaling a healthy, collaborative development environment. This activity is focused on the foundational Cosmos SDK-based application that secures the network and processes cross-chain messages.
What this means: This is neutral for AXL because it shows the core protocol is being actively maintained, which is essential for network security and reliability. However, these are routine commits rather than landmark upgrades.
(Source)
2. Maestro Portal Feature Updates (26 March 2025)
Overview: The Maestro app, part of the Axelar developer suite, released version 0.4.1. This update primarily changed the default RPC URL for the Fantom network to improve reliability and updated internal dependencies.
Earlier patches in this version stream added support for the Flow blockchain, updated smart contract functions, and added backup RPC URLs for all mainnet chains to increase resilience.
What this means: This is bullish for AXL because it improves the developer experience and tooling reliability. Smoother developer tools can lead to more applications being built on Axelar, potentially driving network usage.
(Source)
3. SDK Gas Estimation & Chain Support (18 October 2024)
Overview: Version 0.17.0 of the axelarjs-sdk fixed a UI error related to adding gas for Cosmos chains and added support for "Amplifier" chains. This follows a series of updates throughout 2024 that refined the critical estimateGasFee function for better accuracy, especially for Layer 2 rollups.
These technical improvements help applications provide users with more reliable transaction cost estimates before they sign, reducing failed transactions.
What this means: This is bullish for AXL because more accurate gas estimates lead to a better user experience. When cross-chain transactions are predictable and don't fail due to fee issues, it encourages more people to use the network.
(Source)
Conclusion
Axelar's development trajectory shows a focus on core protocol stability and refining the developer toolkit, with the most recent visible activity centered on the foundational axelar-core code. While major SDK and portal updates occurred over a year ago, the consistent commit history suggests ongoing, behind-the-scenes work to maintain and improve the network's infrastructure. How will the transition of development leadership to Common Prefix influence the pace and direction of future major upgrades?