A TLV (Type-Length-Value) format is used to allow for the backwards-compatible addition of new fields to existing LN message types.
Motivation
OmniBOLT transaction can be embeded into LN messages, so that current ln network can benifit from the liquidity of Omnilayer assets.
Rationale
OmniLayer issues assets on Bitcoin network, it can be used as a settlement system, which has proven mechanism to provent double spent or any other malicious activities onchain.
OmniBOLT transactions are constructed on top of raw omni transactions, and can be used as a quick circulation network. It has it own communication spec, but need to be compatible with existing LN network.
TLV is a right place to put OmniBOLT tx info in. A lnd node will be omni asset aware, if it work with obd, in which case obd works like a plugin to lnd.
A simple workflow is:
lnd receives a message, which contain a TLV field, then lnd redirect it to its obd plugin.
obd parses the value of TLV field,
if it is an OmniBOLT message, obd will execute it.
TLV -- Type Length Value
A TLV (Type-Length-Value) format is used to allow for the backwards-compatible addition of new fields to existing LN message types.
Motivation
OmniBOLT transaction can be embeded into LN messages, so that current ln network can benifit from the liquidity of Omnilayer assets.
Rationale
OmniLayer issues assets on Bitcoin network, it can be used as a settlement system, which has proven mechanism to provent double spent or any other malicious activities onchain.
OmniBOLT transactions are constructed on top of raw omni transactions, and can be used as a quick circulation network. It has it own communication spec, but need to be compatible with existing LN network.
TLV is a right place to put OmniBOLT tx info in. A lnd node will be omni asset aware, if it work with obd, in which case obd works like a plugin to lnd.
A simple workflow is: