omnilaboratory / omnibolt-spec

Facilitate smart assets circulation and exchange in Lightning Network.

OmniBOLT: Facilitates smart assets lightning transactions

• Contact: Neo Carmack([email protected]), Ben Fei([email protected])

Based on the fundamental theory of the Lightning network, the OmniBOLT specification describes how to enable OmniLayer assets to be circulated via lightning channels, and how can smart assets benefit from this novel quick payment theory.

In addition, OmniBOLT provides more flexible contracts for upper-layer decentralized applications. OmniBOLT daemon is a golang implementation of this specification, an open source, off-chain decentralized platform, built upon BTC/OmniLayer network, implements basic HTLC payment, atomic swap of multi-currencies, and more off-chain contracts on the network of smart assets enabled lightning channels.

Features

• Instant payment of smart assets issued on OmniLayer and Etherium(soon future).
• Cross channel atomic swap for various crypto assets.
• Decentralized exchange on top of stable coin enabled lightning channels.

• Automatic market maker and liquidity pool for DEX.

Why OmniBOLT

The decentralized finance industry requires a much more flexible, extensible, and cheaper smart assets circulation solution to solve the main chain scalability problem. The Lightning Network is a solid technology for this problem. Besides the layer-2 protocol BOLT (Basis of Lightning Technology) specification for off-chain bitcoin transfer, we need a protocol to support a wider range of assets for upper-layer applications: payment, game, finance, or scenarios that need stablecoins.

Meanwhile, Omnilayer is an on-chain smart assets issuance technology, which is proven secure and stable. Constructing lightning channels on top of it automatically acquires the ability to issue assets, tamper resistance, and on-chain settlement. This is where OmniBOLT is built upon.

How it works:

1. On-chain protocol is Omnilayer, which is the token issuance and settlement layer;
2. OmniBOLT 2, 3, and 4 form the main network protocols;
3. Applications level consists of contracts for various applications;

OmniBOLT does not issue tokens. All tokens are issued on Omnilayer, and enter the OmniBOLT lightning network through P2(W)SH backed channels, being locked on the main chain, and can be redeemed on the Omnilayer main chain at any time.

Currently supported assets are of:

1. Fixed number tokens: divisible or indivisible
2. Variable number tokens: divisible or indivisible

All assets are fungible assets.

Chapters and Protocol Suite

We not only just list messages and arguments that are used in our implementation, but also complete content that explains why we do so. Most of this spec strictly follows the rules/logic defined in the lightning white paper. The original paper may be hard to read for our programmers, so we draw some diagrams for better understanding. Hope it helps :-)

OmniBOLT #01: Base Protocol and Terminology

OmniBOLT #02: peer-protocol, Poon-Dryja channel open

OmniBOLT #03: RSMC and OmniLayer Transactions

OmniBOLT #04: HTLC and payment Routing

OmniBOLT #05: Atomic Swap Protocol among Channels

OmniBOLT #06: Automatic Market Maker, Liquidity Pool and DEX

OmniBOLT #07: Hierarchical Deterministic (HD) wallet, Invoice Encoding

Technology Guide

OmniBOLT Technology Guide Part I offers quick understanding of the rationale, concepts, architecture of OmniBOLT.

Implementation and API for client applications

Implementation of OmniBOLT specification can be found in this repository OmniBOLT Daemon.

Quick Start

It is recommended to start with a graphic tool to play with OmniBOLT: https://github.com/omnilaboratory/obd#quick-start-on-regtest

Contribution

OmniBolt specification is incubated by Omnilayer.foundation. Any proposal, please submit issues in this repo.