We successfully updated of the Axelar node to the latest version. This update includes important fixes, API improvements, and new features for developers using Axelar, Cosmos SDK, and CosmWasm.
Key Fixes
- Migration Fix in Axelarnet (#2209)
The SendCoinsFromModuleToModule function has been updated, and now it is sufficient to specify the module name instead of the module account address for migration. This simplifies the migration process and improves code readability.
- Dec Range Fix in SDK (#2211)
Stricter checks for the Dec type values in the Cosmos SDK have been implemented. This will help prevent errors when working with fractional numbers. If your code actively uses fractional values, ensure it is compatible with the new requirements.
- Update to Multi-Signature Protobuf Messages (#2232)
The sender field is now deprecated, and a new field with the correct data type has been introduced. If your project works with multi-signature transactions, you will need to update your code to use the new field.
- Distribution Module Updates
- #2234: The begin blocker now uses the wrapped keeper, improving control over distribution logic.
- #2242: The distribution module’s account now has burner rights, allowing it to burn tokens. This important change may affect the tokenomics of your project.
New Features
Custom Fee Distribution (#2231)
Developers now have the ability to customize fee distribution. This is especially useful for projects that implement non-standard reward and fee distribution schemes, providing more flexibility in token management.
Refactoring and Improvements
Code Readability Enhancement in Nexus (#2214)
The variable nextID has been renamed to currIDAndIncr, reflecting its true purpose: the current ID with the ability to increment.
Dependency Updates
- Updated Cosmos SDK and CosmWasm (#2236, #2238).
- Updated wasmvm in Dockerfile (#2237).
- Renamed events in the distribution module (#2235), requiring updates if your project depends on these events.
What This Means for Developers
If your project integrates Axelar or uses Cosmos SDK, be sure to pay attention to the following key points:
1. Distribution Module
- API changes, new custom fee distribution options, and burner rights for module accounts. Make sure to verify how these changes might impact your system.
2. Multi-Signature Transactions
- The update to protobuf messages requires using the new field instead of the deprecated sender. Update your code if your project uses multi-signatures.
3. Updated Dependencies
- Check the compatibility of your code with the new versions of Cosmos SDK, CosmWasm, and WasmVM, as these updates may affect your application’s functionality.
4. Axelarnet Migration Process
- The migration process in Axelarnet is now simpler, thanks to the enhancement in the token transfer function. Ensure your code passes the module name rather than its address.
5. Nexus Identifier Updates
- The change from nextID to currIDAndIncr is important if your code uses these identifiers.
Conclusion
The Axelar node update brings new opportunities to enhance your project’s functionality and security. The main changes involve migration, token distribution, fractional number handling, and multi-signature transactions.
NOWNodes is a blockchain-as-a-service solution that lets users get access to Axelar Nodes and blockbook Explorers via API. The service provides a high-quality infrastructure that is quick, cost-effective, and reliable. We have Service Quality Standards available for all partners.
AXL is under 24/7 surveillance – their availability and relevance are constantly being monitored. Get access to INJ Nodes NOW:
