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 |
Networking | Handshake and encryption in network communications based on Noise_XK (BOLT-8 extract) | Multiple peers | Standard | Proposal | |
16 | Commitment schemes | Anchoring multiple deterministic bitcoin commitments in the same transaction output | Maxim Orlovsky | Standard | Final |
17 | Commitment schemes | TapRet: Taproot script tree-based OP_RETURN deterministic bitcoin commitments | Maxim Orlovsky et al | Standard | Final |
Networking | Native message framing protocol (BOLT-8 extract) | Multiple peers | Standard | Planned | |
19 | Commitment schemes | Reserved for sign-to-contract deterministic bitcoin commitments | | | |
Wallet | RGB fungible assets interface (RGB-20) | Multiple peers | Standard | Final | |
Wallet | RGB non-fungible collectibles interface (RGB-21) | Maxim Orlovsky | Standard | Proposal | |
Wallet | RGB reputation and identity interface (RGB-22) | Maxim Orlovsky, Sabina Sachtachtinskagia | Standard | Draft | |
Wallet | RGB verifiable-unique history log for auditable data (RGB-23) | Maxim Orlovsky, Giacomo Zucco | Standard | Planned | |
Wallet | RGB schema for decentralized global domain name system (RGB-24) | Maxim Orlovsky | Standard | Planned | |
25-31 | Reserved | For the future use by RGB schemata | | | |
32 | Wallet | BIP-32 derivation path extension for read-only wallets | Maxim Orlovsky | Standard | Draft |
Smart contracts | Lightspeed: micro-payments for Lightning Network | Maxim Orlovsky | Draft | | |
Smart contracts | Zero-knowledge arguments for data persistence using probabilistic checkable proofs | Maxim Orlovsky | Standard | Draft | |
Smart contracts | Bifrost: LN message extensions for RGB data propagation | Maxim Orlovsky | Standard | Planned | |
36 | Reserved | For future use by lightning network protocol extensions | | | |
Wallet | Invoicing formats for RGB-20 fungible assets schema | Alekos Filini | Standard | Rejected | |
Wallet | Universal LNP/BP invoices | Maxim Orlovsky | Standard | Draft | |
39 | Reserved | For future use by lightning network protocol extensions | | | |
Smart contracts | Storm: trustless storage with escrow contracts | Maxim Orlovsky | Standard | Draft | |
41 | Smart contracts | Lightning network message extensions for Storm | Maxim Orlovsky | Standard | Planned |
42 | Reserved | For future use by lightning network protocol extensions | | | |
Wallet | RGB-enabled BIP43 purpose field & identity system | Maxim Orlovsky | Standard | Draft | |
44 | Wallet | Script templating: BIP-32 & LNPBP-43 key derivations within for non-miniscript-compatible Bitcoin scripts | Maxim Orlovsky | Standard | Draft |
45 | Smart contracts | Lightning network message extensions for decentralized exchange functionality | Maxim Orlovsky | Standard | Planned |
46 | Wallet | Deterministic derivation paths for LNP | Maxim Orlovsky | Draft | |
47,48 | Reserved | For future use by lightning network protocol extensions | | | |
49 | Smart contracts | Synchronized multi-hop state updates via delegation in Lightning network | Maxim Orlovsky, Christian Decker | Standard | Planned |
Smart contracts | Bifrost: generalized Lightning network protocol core | Maxim Orlovsky | Standard | Planned | |
Smart contracts | Bifrost: channel management protocol | Maxim Orlovsky | Standard | Draft | |
52 | Smart contracts | Bifrost routed messaging system based on Sphix protocol | Maxim Orlovsky | Standard | Draft |
Smart contracts | Milti-peer payment channels for Bifrost | Maxim Orlovsky | Standard | Draft | |
54 | Smart contracts | Channel factories based on Bifrost protocol | Maxim Orlovsky | Standard | Draft |
Smart contracts | HTLC channel synchronization in Bifrost | Maxim Orlovsky | Standard | Draft | |
56 | Smart contracts | PTLC channel synchronization in Bifrost | Maxim Orlovsky | Standard | Draft |
57 | Smart contracts | Decentralized naming & name resolution system | Maxim Orlovsky | Standard | Planned |
Commitment schemes | Apophis: distributed elliptic curve-based key creation with shared secrets | Maxim Orlovsky | Standard | Draft | |
Smart contracts | Typhon: trustless Bitcoin sidechains | Maxim Orlovsky | Standard | Draft | |
Smart contracts | Ibiss: incentive-based interactive anonymous settlement scheme for computation integrity arguments | Maxim Orlovsky, Sabina Sachtachtinskagia | Informational | Draft | |
Smart contracts | Toth: incentive-based interactive settlement scheme for computation integrity arguments with reputation | Maxim Orlovsky, Sabina Sachtachtinskagia | Informational | Draft | |
Smart contracts | Prometheus: trustless multiparty computing with escrow & arbitration using Ibiss protocol on bitcoin blockchain | Maxim Orlovsky | Standard | Draft | |
63 | Smart contracts | Prometheus+: prometheus over LN with tokenized RGB reputation | Maxim Orlovsky | Standard | Planned |
64-79 | Reserved | For the future use by lightning network protocol extensions | | | |
Commitment schemes | Merkle mountain ranges | Peter Todd | Standard | Final | |
81 | Commitment schemes | Tagged merkle trees for client-side-validation | Maxim Orlovsky, Peter Todd | Standard | Draft |
82 | Commitment schemes | OpenTimestamps bitcoin transaction commitments | Peter Todd | Standard | Final |
83 | Commitment schemes | OpenTimestamps proof construction & verification | Peter Todd | Standard | Final |
83 | Commitment schemes | OpenTimestamps proof serialization | Peter Todd | Standard | Final |
84 | Commitment schemes | OpenTimestamps calendar and attestation services | Peter Todd | Standard | Final |
85-89 | Reserved | | | | |
Smart contracts | AluVM: virtual machine for client-side-validation | Maxim Orlovsky | Standard | Draft | |
91 | Smart contracts | AluVM extended instructions for handling RGB state validation | Maxim Orlovsky | Standard | Planned |
92-99 | Reserved | For future use by AluVM-specific standards | | | |
100 | Reserved | For future use by a scalable & confidential single-use-seal commitment layer 1 | | | |
- 1.Discreet log contracts:
- 2.
Name | Description | Examples |
|---|---|---|
Commitment schemes | Commitment schemes used in client-side-validation | Commitment schemes, zero knownledge |
Wallet | Standards for wallet and other client-facing applications | Derivation paths, APIs, RGB asset schemata |
Networking | P2P network communication protocols | Network encryption, framing, connectivity etc |
Smart contracts | Distributed smart contract execution environment | Scriptless scripts, RGB, lightning network applications, virtual machines etc |
Last modified 1mo ago