An omni bridge

The HTLC is a smart contract that must be deployed on both the source and target blockchains of the bridge. We provide an implementation of the HTLC for the Ethereum Virtual Machine (EVM), which can be deployed on all EVM-based blockchains, including Polygon, BSC, HarmonyOne, Arbitrum, ETC, CyberMiles, as well as many parachains in Polkadot, Cosmos, and Oasis ecosystems. Obridge has significantly optimized the EVM-based HTLC and achieves a 50% gas fee reduction compared with previous generations of HTLCs (e.g., cBridge contracts).

On Bitcoin (BTC) and similar blockchains (e.g., BCH, BSV, Doge etc.), the HTLC contracts could be written in Bitcoin Scripts.

However, an increasing number of blockchains feature their own smart contract languages (Rust, Go, C/C++, Python, JavaScript etc.) and VMs (typically WebAssembly or WASM). Popular examples include Solana, Polkadot / Substrate, ParaState, NEAR, Avalanche, Algorand, Hashgraph, Cosmos, EOS, Oasis, FileCoin and many others. While those blockchains may or may not support the EVM, their β€œnative” smart contract VM supports the most complete feature set at the lowest gas cost. It is important for the atomic swap bridge to be polyglot and support all those native languages and VMs. That is why the Obridge is known as the omni bridge. It already supports non-EVM blockchains and is adding more.

Last updated