bLIP stands for Bitcoin Lightning Improvement Proposal. A bLIP is a design document providing information to the Lightning community, or describing a new feature for the Lightning Network. The bLIP should provide a concise technical specification of the feature and a rationale for the feature. The bLIP author is responsible for building consensus within the community and documenting dissenting opinions. Importantly, if a feature is intended to become universal or near universal, it must be a BOLT.
People wishing to submit bLIPs (Bitcoin Lightning Improvement Proposals) should first propose their idea to the Lightning development mailing list. After discussion, please open a PR. After copy-editing and acceptance, it will be published here.
For more detail on the process, please read bLIP-0001 and bLIP-0002.
| Number | Title | Author | Status |
|---|---|---|---|
| 1 | bLIP Process | Ryan Gentry | Active |
| 2 | Reserved Values | Bastien Teinturier | Active |
| 3 | Keysend | Valentine Wallace | Active |
| 4 | Experimental Endorsement | Carla Kirk-Cohen | Active |
| 10 | Podcasting 2.0 | Satoshis Stream | Active |
| 11 | NameDesc | Hampus Sjöberg | Active |
| 17 | Hosted Channels | Anton Kumaigorodskiy | Active |
| 25 | Forward less than onion value | Valentine Wallace | Active |
| 32 | Onion Message DNS Resolution | Matt Corallo | Active |
| 50 | LSPS0: LSP Spec Transport Layer | ZmnSCPxj jxPCSnmZ | Active |
| 51 | LSPS1: Channel Requests | Severin Bühler | Active |
| 52 | LSPS2: JIT Channel Negotiation | ZmnSCPxj jxPCSnmZ | Active |