The Kinesis Bridge, built by Ideasoft and powered by Hyperlane, is Kadena's first decentralized cross-chain asset bridge enabling secure token transfers between Kadena and the broader crypto ecosystem.

V1 of the Kinesis Bridge enables transfers between Ethereum mainnet and Kadena. In a staggered launch beginning January 2025, we will integrate support for Arbitrum, Avalanche, BSC, Celo, Gnosis, Moonbeam, Optimism, Polygon, and Celestia. Looking further ahead, thanks to Hyperlane's permissionless architecture, future versions of the bridge will enable users to transfer assets and create interchain applications acrossany chain that supports Hyperlane.

How does Hyperlane work?

Hyperlane is a permissionless interoperability layer, empowering smart contract developers to transfer various data types between blockchains. Developers can leverage Hyperlane for tasks such as moving tokens and executing function calls, enabling the creation of interchain applications accessible across different blockchain networks.

With Hyperlane, user engagement is facilitated through mailbox smart contracts, providing an on-chain messaging interface for the seamless exchange of interchain messages. Hyperlane employs a modular security approach, allowing applications to customize their security model by choosing from a selection of Interchain Security Modules (ISMs).

The key component, known as Warp Routes, enable permissionless asset transfers between blockchains. Each Warp Route functions as a separate bridge with its own security model, secured by Sovereign Consensus.

Hyperlane's permissionless nature empowers any blockchain to establish Warp Routes, streamlining the exchange of value with existing Hyperlane-supported chains. Users gain the ability to independently create and deploy interchain assets, reducing dependence on the core team for asset whitelisting and encouraging a broader range of assets and interchain activities.

The operational process involves a classic lock and mint bridge mechanism. Collateral is locked on the home chain, and a wrapped version is minted on the destination chain. This process incorporates siloed contracts and asset security models specified by the Warp Route deployer. Essentially, each asset is treated as its own isolated application within the overarching Hyperlane framework.