List of specifications
LNP/BP stands for "Bitcoin Protocol / Lightning Network Protocol". This set of specifications covers standards & best practices for Layer 2, 3 solutions (and above) in cases when they do not require soft- or hard-forks on the Bitcoin blockchain level and are not directly related to issues covered in Lightning Network RFCs (BOLTs).
Basically, LNP/BPs cover everything that can be anchored to Bitcoin transactions, defines primitives for L2+ solution design and describes complex use cases which can be built from some primitives. This allows such solutions as financial assets, storage, messaging, computing and different forms of secondary markets leveraging Bitcoin security model and Bitcoin as a method of payment/medium of exchange.
Criteria for a LNP/BP specification proposal:
- Should not be covered by existing or proposed BIPs
- Should not cause soft- or hard-fork in Bitcoin blockchain (but may depend on soft-forks from an existing BIP proposals)
- Should not distort Bitcoin miner's economic incentives
- Should not pollute Bitcoin blockchain with unnecessary non-transaction related data or have to maintain such pollution as low as possible
- Must not require a utility or security tokens to function (but may enable creation of digital assets or tokenized physical goods)
- Must not depend on non-bitcoin blockchains (but may be applicable to other blockchains)
No | Vertical | Title | Authors | Type | Status |
---|---|---|---|---|---|
Commitment schemes | Key tweaking: collision-resistant elliptic curve-based commitments | Maxim Orlovsky et al | Standard | Proposal | |
Commitment schemes | Script tweaking: deterministic embedding of cryptographic commitments into script pubkeys | Maxim Orlovsky et al | Standard | Proposal | |
Commitment schemes | Deterministic definition of transaction output containing cryptographic commitment | Giacomo Zucco et al | Standard | Proposal | |
Commitment schemes | Multi-protocol commitment scheme with zero-knowledge provable uniqueness | Maxim Orlovsky | Standard | Proposal | |
Wallet | Universal short Bitcoin identifiers for blocks, transactions and their inputs & outputs | Christian Decker, Maxim Orlovsky | Standard | Proposal | |
Commitment schemes | PayTweak: pay-to-contract deterministic bitcoin commitments | Maxim Orlovsky | Standard | Draft | |
7 | Commitment schemes | Strict encoding and commitment-encode protocols | Peter Todd, Maxim Orlovsky | Standard | Planned |
Commitment schemes | Single-use-seals | Peter Todd, Maxim Orlovsky | Informational | Draft | |
Commitment schemes | Client-side-validation | Peter Todd, Maxim Orlovsky | Informational | Draft | |
Commitment schemes | Bitcoin transaction output-based single-use-seals | Maxim Orlovsky et al | Standard | Proposal | |
Smart contracts | RGB: Client-validated confidential smart contracts using bitcoin transaction graphs for Bitcoin and Lightning Network | Maxim Orlovsky et al | Informational | Proposal | |
12 | Smart contracts | RGB Schema: client-side validation rules for RGB smart contracts | Maxim Orlovsky | Standard | Planned |
13 | Smart contracts | RGB client-side verification and data serialization | Maxim Orlovsky | Standard | Planned |
14 | Wallet | Bech32 encoding for client-validated data | Maxim Orlovsky | Standard | Planned |