From: thepipeline_xyz

Security and decentralization are fundamental pillars in the design and operation of blockchain networks and their associated infrastructure. The history of decentralized finance (DeFi) has highlighted the critical importance of these aspects, particularly in cross-chain solutions.

The Problem with Centralized Bridges

Historically, many early cross-chain bridges, such as Ren protocol and Multi-chain, operated as centralized entities. These bridges typically relied on a founder or a small centralized group holding all funds in a single key [00:04:02]. This centralized control presented a significant vulnerability: once the key was compromised, all funds were at risk, which proved to be “just a matter of time” [00:04:10].

Major hacks in the DeFi space, including the Harmony hack, the Ronin hack, and the Multi-chain incident, collectively resulted in billions of dollars lost. These incidents “all happened because of centralization” [00:04:14], underscoring the severe challenges in blockchain system design inherent in centralized bridging solutions.

Axelar’s Decentralized Approach

Axelar, as an interoperability network, adopted a “very different approach to solving the cross chain problem” by not being a bridge itself, but rather a messaging platform [00:04:26]. Its core design focuses on enhancing security and decentralization:

  1. Blockchain Architecture: Axelar is structured as a blockchain built on the Cosmos SDK [00:06:07]. This architecture enables “many to many connectivity” [00:05:22], allowing a single connection to Axelar to route messages to any of its 56+ connected blockchains [00:03:35]. This contrasts with competitors like Wormhole and Chainlink CCIP, which primarily offer “pairwise connectivity,” making it harder to add new chains [00:05:47].
  2. Decentralized Validator Set: A crucial aspect of Axelar’s decentralization and security is its fully decentralized validator set [00:06:09]. With 75 validators, many of whom are familiar from the Ethereum mainnet [00:06:14], attacking the network to steal funds would require corrupting a majority of these validators [00:06:26]. This makes Axelar “almost as secure as all of the chains that it connects to” [00:06:36], and it is significantly more decentralized than many competitors, with five times more validators than Wormhole (75 vs. 19) [00:06:55].

Mitigating Interoperability Risk

Regardless of whether assets are deployed as native or wrapped tokens, the security of the underlying bridging infrastructure is paramount [00:22:26]. Axelar implements several layers of security to minimize potential damage:

  • Decentralization: As discussed, the decentralized validator set removes the most common attack vector seen in centralized bridges [00:23:16].
  • Rate Limiting: This simple code check can be added to every transaction to cap the amount of funds that can be moved within a certain timeframe, effectively minimizing the impact of a hack [00:23:46]. Axelar’s architecture allows for customizable rate limits on the Axelar blockchain itself, containing damage even if a connected blockchain experiences a break [00:24:09]. While not perfect for very high throughput chains, rate limiting can still “minimize the damage compared to the the full tvl of the different assets” [00:27:24].
  • Multi-Party Approval (External): For extreme security, applications can implement multi-party approval systems. For example, the Lido community decided to work jointly with Axelar and Wormhole, requiring approval from both validator sets before an asset is minted [00:25:00]. This layered approach combines two independent implementations with stacked rate limits, creating “the most secure thing we’ve seen in terms of cross chain security so far” [00:25:36].

Interchain Token Service (ITS)

Axelar’s Interchain Token Service (ITS), currently in beta, exemplifies the ethos of decentralization and permissionless access. It is described as the “first code-free permissionless tokenization and bridging solution” [00:18:40]. Anyone, regardless of their development skills, can use a front-end to take their token cross-chain in minutes [00:20:54]. This feature is expected to transform token launches, making it “meaningless” to launch a token on only a single chain [00:20:17], and making cross-chain token launches the standard from day one [00:20:20].

The Future of Interoperability

The evolution of interoperability sees a shift from projects being content on a single chain to planning deployments across multiple chains from the outset [00:16:01]. This is driven by the rapid growth in the number of chains and the shifting landscape of liquidity and users [00:16:23].

Ultimately, interoperability is not about a “killer use case” but about improving the overall “user experience” [00:31:12], making Web3 as easy to use as Web2 [00:31:18]. The goal is to abstract away the underlying blockchain complexities from the user, allowing them to focus solely on assets and applications [00:31:35]. This vision suggests that interoperability will become an integral part of virtually every use case, from DeFi and gaming to real-world asset tokenization and NFTs [00:32:11].