LNP/BP 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)
List of current LNP/BP proposals
No | Vertical | Title | Authors | Type | Status |
---|---|---|---|---|---|
1 | Cryptographic primitives | Key tweaking: collision-resistant elliptic curve-based commitments | Maxim Orlovsky et al | Standard | Proposal |
2 | Bitcoin protocol | Deterministic embedding of cryptographic commitments into bitcoin transaction output | Maxim Orlovsky et al | Standard | Proposal |
3 | Bitcoin protocol | Deterministic definition of transaction output containing cryptographic commitment | Giacomo Zucco et al | Standard | Proposal |
4 | Cryptographic primitives | Multi-message commitment scheme with zero-knowledge provable unique properties | Maxim Orlovsky | Standard | Proposal |
5 | Bitcoin protocol | Universal short Bitcoin identifiers for blocks, transactions and their inputs & outputs | Christian Decker, Maxim Orlovsky | Standard | Proposal |
6 | Bitcoin protocol | Deterministic bitcoin commitments | Maxim Orlovsky | Standard | Draft |
7 | Consensus layer | Strict encoding | Peter Todd, Maxim Orlovsky | Standard | Planned |
8 | Cryptographic primitives | Single-use-seals | Peter Todd, Maxim Orlovsky | Informational | Draft |
9 | Consensus layer | Client-side-validation | Peter Todd, Maxim Orlovsky | Informational | Draft |
10 | Bitcoin protocol | Bitcoin transaction output-based single-use-seals | Maxim Orlovsky et al | Standard | Proposal |
11 | Smart contracts | RGB: Client-validated confidential smart contracts using bitcoin transaction graphs for Bitcoin and Lightning Network | Maxim Orlovsky et al | Informational | Proposal |
12 | Consensus layer | RGB Schema: client-side validation rules for RGB smart contracts | Maxim Orlovsky | Standard | Planned |
13 | Consensus layer | RGB client-side verification and data serialization | Maxim Orlovsky | Standard | Planned |
14 | Smart contracts | Bech32 encoding for client-validated data | Maxim Orlovsky | Standard | Planned |
15 | Internet2 | Handshake and encryption in network communications based on Noise_XK (BOLT-8 extract) | Multiple peers | Standard | Proposal |
16 | Internet2 | LNPBP-15 handshake over WebSockets | Maxim Orlovsky | Standard | Planned |
17 | Internet2 | Microservice interprocess communications | Maxim Orlovsky | Informational | Planned |
18 | Lightning network protocol | Native message framing protocol (BOLT-8 extract) | Multiple peers | Standard | Planned |
19 | Internet2 | ZMQ-based RPC and ESB protocols for microservices | Multiple peers | Standard | Planned |
20 | Smart contracts | RGB fungible assets schema (RGB-20) | Multiple peers | Standard | Final |
21 | Smart contracts | RGB schema for NFTs representing ownership rights (RGB-21) | Maxim Orlovsky | Standard | Proposal |
22 | Smart contracts | RGB reputation and identity schema (RGB-22) | Maxim Orlovsky, Sabina Sachtachtinskagia | Standard | Draft |
23 | Smart contracts | RGB verifiable-unique history log for auditable data (RGB-23) | Maxim Orlovsky, Giacomo Zucco | Standard | Planned |
24 | Smart contracts | RGB-24 schema for decentralized global name system (DGNS) | Maxim Orlovsky | Standard | Planned |
30 | Smart contracts | RGB-wrapped native blockchain assets schema (RGB-30) | Maxim Orlovsky | Standard | Planned |
25-29, 31 | Reserved | For the future use by RGB schemata | |||
32 | Bitcoin | BIP-32 derivation path extension for read-only wallets | Maxim Orlovsky | Standard | Draft |
33 | Lightning network protocol | Lightspeed: micro-payments for Lightning Network | Maxim Orlovsky | Draft | |
34 | Cryptographic primitives | Zero-knowledge arguments for data persistence using probabilistic checkable proofs | Maxim Orlovsky | Standard | Draft |
35 | Lightning network protocol | Bifrost: LN message extensions for RGB data propagation | Maxim Orlovsky | Standard | Planned |
36 | Internet2 | Recommendations for API design | Maxim Orlovsky | Informational | Draft |
37 | Smart contracts | Invoicing formats for RGB-20 fungible assets schema | Alekos Filini | Standard | Rejected |
38 | Smart contracts | Universal LNP/BP invoices supporting Bitcoin, LN & RGB | Maxim Orlovsky | Standard | Draft |
39 | Bitcoin protocol | Bitcoin transaction output-based single-use-seals with sign-to-contract commitments | Maxim Orlovsky et al | Standard | Planned |
40 | Smart contracts | Storm: trustless storage with escrow contracts | Maxim Orlovsky | Standard | Draft |
41 | Lightning network protocol | Lightning network message extensions for Storm | Maxim Orlovsky | Standard | Planned |
42 | Internet2 | Uniform encoding for internet2 addresses | Maxim Orlovsky | Draft | |
43 | Bitcoin protocol | RGB-enabled BIP43 purpose field & identity system | Maxim Orlovsky | Standard | Draft |
44 | Bitcoin protocol | Script templating: BIP-32 & LNPBP-43 key derivations within for non-miniscript-compatible Bitcoin scripts | Maxim Orlovsky | Standard | Draft |
45 | Lightning network protocol | Lightning network message extensions for decentralized exchange functionality | Maxim Orlovsky | Standard | Planned |
46 | Lightning network protocol | Deterministic derivation paths for LNP | Maxim Orlovsky | Draft | |
47,48 | Reserved | For future use by lightning network protocol extensions | |||
49 | Lightning network protocol | Synchronized multi-hop state updates via delegation in Lightning network | Maxim Orlovsky, Christian Decker | Standard | Planned |
50 | Lightning network protocol | Bifrost: generalized Lightning network protocol core | Maxim Orlovsky | Standard | Planned |
51 | Lightning network protocol | Bifrost: channel management protocol | Maxim Orlovsky | Standard | Draft |
52 | Lightning network protocol | Bifrost routed messaging system based on Sphix protocol | Maxim Orlovsky | Standard | Draft |
53 | Lightning network protocol | Milti-peer payment channels for Bifrost | Maxim Orlovsky | Standard | Draft |
54 | Lightning network protocol | Channel factories based on Bifrost protocol | Maxim Orlovsky | Standard | Draft |
55 | Lightning network protocol | HTLC channel synchronization in Bifrost | Maxim Orlovsky | Standard | Draft |
56 | Lightning network protocol | PTLC channel synchronization in Bifrost | Maxim Orlovsky | Standard | Draft |
57 | Lightning network protocol | Decentralized naming & name resolution system | Maxim Orlovsky | Standard | Planned |
58 | Cryptographic primitives | Apophis: distributed elliptic curve-based key creation with shared secrets | Maxim Orlovsky | Standard | Draft |
59 | Bitcoin protocol | Typhon: trustless Bitcoin sidechains | Maxim Orlovsky | Standard | Draft |
60 | Game theory | Ibiss: incentive-based interactive anonymous settlement scheme for computation integrity arguments | Maxim Orlovsky, Sabina Sachtachtinskagia | Informational | Draft |
61 | Game theory | Toth: incentive-based interactive settlement scheme for computation integrity arguments with reputation | Maxim Orlovsky, Sabina Sachtachtinskagia | Informational | Draft |
62 | Smart contracts | Prometheus: trustless multiparty computing with escrow & arbitration using Ibiss protocol on bitcoin blockchain | Maxim Orlovsky | Standard | Draft |
63 | Smart contracts | Prometheus+: trustless multiparty computing with escrow & arbitration using Ibiss2 protocol over LN with tokenized RGB reputation | Maxim Orlovsky | Standard | Planned |
64-79 | Reserved | For the future use by lightning network protocol extensions | |||
80 | Cryptographic primitives | Merkle mountain ranges | Peter Todd | Standard | Final |
81 | Cryptographic primitives | Tagged merkle trees for client-side-validation | Maxim Orlovsky, Peter Todd | Standard | Draft |
82 | Bitcoin protocol | OpenTimestamps bitcoin transaction commitments | Peter Todd | Standard | Final |
83 | Smart contracts | OpenTimestamps proof construction & verification | Peter Todd | Standard | Final |
83 | Smart contracts | OpenTimestamps proof serialization | Peter Todd | Standard | Final |
84 | Smart contracts | OpenTimestamps calendar and attestation services | Peter Todd | Standard | Final |
85 | Bitcoin protocol | Strict encoding of Bitcoin-related data types | Maxim Orlovsky | Standard | Planned |
86 | Smart contracts | AluVM: virtual machine for client-side-validation | Maxim Orlovsky | Standard | Draft |
87 | Smart contracts | AluVM extended instructions for handling RGB state validation | Maxim Orlovsky | Standard | Planned |
88-89 | Reserved | For future use by AluVM-specific standards | |||
[90] | Cryptographic primitives | Signature tweaking: collision-resistant BIP340-based commitments | Maxim Orlovsky et al | Standard | Draft |
[91] | Cryptographic primitives | Signature tweaking: collision-resistant ECDSA-based commitments | Maxim Orlovsky et al | Standard | Draft |
92 | Bitcoin protocol | Deterministic embedding of cryptographic commitments into transaction input | Maxim Orlovsky et al | Standard | Draft |
93-99 | Reserved | For future use | |||
100 | Bitcoin protocol | Scalable & confidential single-use-seal commitment layer 1 | Standard | Brainstorming |
Invited or planned proposals to join LNP/BP standards family
- Discreet log contracts: deterministic transaction structure, embedding into lightning network, wire protocols
- Different pre-Schnorr schemes for scriptless scripts
- Generalized lightning network standartisation and related eltoo and PTLC proposals
Verticals for LNP/BP proposals:
Name | Description | Examples |
---|---|---|
Cryptographic primitives | Basic cryptographic functions | Commitment schemes, zero knownledge |
Consensus layer | Standards critical for consensus in distributed systems | Data encoding, validation rules |
Internet2 | Standards for end-to-end encrypted censorship-resistant networking communications (Internet2) | Network encryption and data serialization; virtual machines for distrubited systems |
Bitcoin protocol | Changes at the level of bitcoin protocol | Commitments in bitcoin transactions, single-use-seals applications to bitcoin, layer 1 enhancements |
Lightning network protocol | Changes to lighting-network related standards and state channel mechanics | New types of state channels, new lightning network message types, changes in channel transaction structure |
Smart contracts | Distributed smart contract execution environment | Bitcoin scripts, scriptless scripts, RGB |
Game theory | Game-theoretical setups for trustless protocols | Incentive schemes with bitcoin transactions & RGB smart contracts |