portfolio

Connecting New Chains to Axelar

Since 2023 we have connected new blockchains to the Axelar cross-chain network: MultiversX support in Axelar's verifier daemon and local dev tooling, relayers built on the Amplifier API for ZK Stack and Stacks, and deployment scripts merged into Axelar's official repositories. The work covers the off-chain plumbing that lets messages and tokens move between these chains and the rest of Axelar.
Blockchain Integration
Backend
Smart Contracts
Frontend
Axelar Integration logo
Tools
Rust
nest.js
node.js
Solidity
react.js
Docker

The problem: every new chain needs its own plumbing

Axelar lets applications send messages and tokens between chains. With Amplifier, Axelar made chain onboarding permissionless, but each new chain still needs real engineering: verifiers must understand its transactions and finality, a relayer must move messages between the chain and Axelar, gateway contracts must be deployed and wired to Axelar's CosmWasm contracts, and developers need examples and a local environment.

We have done this work for several chains, starting with MultiversX in 2023 and continuing with ZK Stack and Stacks through 2025, contributing to forks of Axelar's own repositories and to purpose built relayers.

MultiversX: from local dev to verifier support

Our first integration brought MultiversX into Axelar's developer tooling. We added MultiversX support to axelar-local-dev, including Interchain Token Service (ITS) support, contributed upstream as pull requests #104 and #106, and built MultiversX examples in axelar-examples: cross-chain contract calls, remote interchain token deployment and token transfers in both directions between EVM chains and MultiversX, with tests and pipelines.

For Amplifier we added MultiversX support to ampd, the daemon verifiers run to check cross-chain events (upstream PR #466), followed by fixes to nonce handling, a transaction hash message id format (#528), an update to the signers hash after contract changes, and transaction finality verification (#765).

ZK Stack: gateway deployment and a demo bridge

In 2024 we connected a ZK Stack chain to Amplifier. ZKsync's EVM does not support create2 and create3 the usual way, so contract addresses cannot be precomputed, while Axelar's CosmWasm contracts need the gateway's domain separator up front. We solved this with a three step deployment: an initial gateway whose proxy address is reused, the CosmWasm contracts, then a full gateway implementation upgraded in place using the weighted signers queried from Axelar.

We wrote Hello World and SimpleBridge examples deployable on the ZK Stack chain, Avalanche Fuji, MultiversX and Stellar, built a NestJS relayer on the Amplifier API (PostgreSQL, Redis, Docker), and shipped a React demo dApp bridging between the ZK Stack chain and Fantom.

Stacks: relayer, proposal and official deploy scripts

For Stacks we built a dedicated relayer on the Amplifier GMP API, developed from October 2024 to May 2025, with an Axelar event processor, PostgreSQL and Redis, and unit and end to end tests. We drafted the Stacks integration proposal for Axelar's Amplifier Advisory Committee, including a reference to the external audit of the contracts.

We then wrote the Stacks deployment scripts in axelar-contract-deployments: gateway setup with an owner wallet, transfer of ownership to the governance contract, verifier thresholds, confirmation height and ITS translator configuration. They were merged upstream (PR #761) and used to deploy Stacks on Axelar's devnet-amplifier and stagenet environments. We also handled Sui testnet contract version and address updates in a fork of axelar-cgp-sui.

Outcome

Across these integrations our work landed in Axelar's own repositories (ampd, local dev, deployment scripts) rather than staying in private forks, and each chain gained the full set of pieces it needs: verifier support, a relayer, deployed and configured gateways, and examples developers can start from.

The recurring lesson is that the hard parts are chain specific details, such as finality rules, address derivation and deployment ordering, which is where we spent most of the effort.