Omnity is an omni-chain interoperability protocol built by Octopus Network on the Internet Computer (IC) specially designed to fit the modular blockchain landscape. It is implemented by a set of smart contracts deployed on IC.
- E : Settlement chains. Currently we have the Bitcoin chain and ICP as the settlement chains.
- S : Execution chains. Currently we have the ICP, Bevm, Bitlayer, B² Network, X Layer, and Merlin as the execution chains.
- Ticket: A transaction message.
- Hub: A center point for chain and token registration, both settlement chains and execution chains are listed in the hub. AS a relayer gathering the tickets, Hub is based on the publisher/subscriber pattern.
- Customs: The Customs is where the assets are listed. The Customs generates transfering tickets.
- Route: Each route represents a execution chain. The Routes generates redeeming tickets.
- Port: Executes the directives from the Hub, mints tokens for cross-chain assets from the settlement chains, processes token transport and token redeem requests from token holders.
- Gate represents Customs in this image.
- Spoke represents Route in this image.
- Bitcoin Token Canister: A solution for fetching the Runes information detail. We have finished transplanting the ord indexer to ICP. The Bitcoin header API will help the ord canister remove its trust assumption on RPC services.
- Bitcoin Canister: A native Bitcoin integration on ICP, the gateway where the bitcoin address can fetch its status like balance and make transactions through the provided APIs.
- Bitcoin (https://bitcoin.org/en/)
- ICP (https://internetcomputer.org/)
- Bevm (https://www.bevm.io/)
- Bitlayer (https://www.bitlayer.org/)
- B² Network (https://www.bsquared.network/)
- X Layer (https://www.okx.com/xlayer)
- Merlin (https://merlinchain.io/)
- Bob (https://www.gobob.xyz/)
- Rootstock (https://rootstock.io/)
This repository has been audited by Blocksec. See the report.