Deep Dive
1. SDK Gas Fix & Amplifier Support (18 October 2024)
Overview: This update to the Axelar JavaScript SDK fixed a bug that prevented users from correctly adding transaction fees when bridging from Cosmos-based chains via the Axelarscan interface. It also prepared the SDK to work with new "Amplifier" chains.
The primary fix resolved an error in the gas estimation logic for these specific transactions. The addition of Amplifier chain configs future-proofs the toolkit for developers building on upcoming networks integrated with Axelar.
What this means: This is neutral for AXL as it's a maintenance update. It ensures a smoother experience for users moving assets between chains, reducing failed transactions due to fee errors, which supports overall network reliability.
(Source)
2. Maestro App Updates & Flow Support (26 March 2025)
Overview: This patch for the Maestro application (part of the Interchain Token Service) introduced several minor improvements and added compatibility with the Flow blockchain.
Changes included updating default RPC URLs for stability, fixing token display issues, and optimizing search queries. The integration of Flow allows developers on that network to use Axelar's tools for creating and managing cross-chain tokens.
What this means: This is bullish for AXL because it expands the protocol's utility to another ecosystem (Flow). A broader developer base and more supported chains can drive increased usage of Axelar's bridging and token services.
(Source)
3. Core Protocol Type Generation (29 January 2026)
Overview: This activity in the axelarjs-types repository shows the generation of new type definitions, which are the essential blueprints for how software interacts with the Axelar blockchain's core logic.
This work is tied to an upgrade of the underlying axelar-core software, ensuring all development tools and applications have accurate, up-to-date instructions for communicating with the network, which is critical after any protocol change.
What this means: This is bullish for AXL as it reflects active, low-level development of the core protocol. Keeping these foundational systems modern and compatible is essential for security, enabling new features, and maintaining the network's long-term technical health.
(Source)
Conclusion
Axelar's codebase is being maintained across the stack—from user-facing tools to core protocol definitions—focusing on reliability, expanded ecosystem support, and foundational upgrades. How will the completion of the core axelar-core upgrade influence the next wave of chain integrations?