📅 Original date posted:2021-12-10
📝 Original message:
Hi all,
Earlier this year, I emailed this mailing list about bitcoin Lightning
Improvement Proposals (bLIPs) [1] as a way to help standardize
community-driven app layer and protocol extension development. Today, I am
excited to let you know that the first two bLIPs specifying the process
have been merged [2] and that we are ready to start receiving proposals!
Here are few example proposals I have my eyes on: Val's Keysend bLIP [3],
the Sphinx team's LUMO messaging format [4], Satoshi's Stream's TLV
registry [5], Lightning Node Connect [6], niftynei's accounting
standardization work, some of Impervious's LN-native communications
work, LND's Static Channel Backup system... and I am sure there are many
more!
Please don't hesitate to reach out if you're interested in writing a bLIP
and want help. We're excited about getting this process going!
As a reminder, a bLIP is a design document providing information to the
Lightning community, or describing a new feature for the Lightning Network,
and should provide a concise technical specification of the feature and a
rationale for the feature. Importantly, if a feature is intended to become
universal or near universal, it must be a BOLT [7].
Because of this distinction, the bLIP editors do not pass judgment on
bLIPs, but only monitor bLIP changes, and update bLIP headers as
appropriate. So long as you check the mailing list to ensure nobody has
made a similar proposal before, fill out the required sections specified in
bLIP-0001, and reserve the required feature bit, message type, or TLV in
the bLIP-0002 registry, we are more than happy to merge proposals into the
repo.
Best,
Ryan
[1]
https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-June/003086.html
[2] https://github.com/lightning/blips
[3] https://github.com/lightning/blips/pull/5
[4] https://github.com/stakwork/lumo-spec
[5]
https://github.com/satoshisstream/satoshis.stream/blob/main/TLV_registry.md
[6]
https://lightning.engineering/posts/2021-11-30-lightning-node-connect-deep-dive/
[7] https://github.com/lightning/bolts
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211210/2d4236c5/attachment.html>;
Ryan Gentry [ARCHIVE] /
npub1jk…f6y7d
2023-06-09 13:04:45
in reply to nevent1q…peq3
Author Public Key
npub1jk0t9q8dag7adpswdsgl6phy603shac5s2fp0lpxwwmpmatkzwas8f6y7dPublished at
2023-06-09 13:04:45Event JSON
{
"id": "dd15f42968aeb39adbca4067e8d5476537d7b303145b366120681641e130bd0e",
"pubkey": "959eb280edea3dd6860e6c11fd06e4d3e30bf714829217fc2673b61df57613bb",
"created_at": 1686315885,
"kind": 1,
"tags": [
[
"e",
"806cd26fd0fb98d5b9f6708e2b27e7d03b6e94db0d2f2d807f42c6994e1aa021",
"",
"reply"
],
[
"p",
"9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c"
]
],
"content": "📅 Original date posted:2021-12-10\n📝 Original message:\nHi all,\n\nEarlier this year, I emailed this mailing list about bitcoin Lightning\nImprovement Proposals (bLIPs) [1] as a way to help standardize\ncommunity-driven app layer and protocol extension development. Today, I am\nexcited to let you know that the first two bLIPs specifying the process\nhave been merged [2] and that we are ready to start receiving proposals!\n\nHere are few example proposals I have my eyes on: Val's Keysend bLIP [3],\nthe Sphinx team's LUMO messaging format [4], Satoshi's Stream's TLV\nregistry [5], Lightning Node Connect [6], niftynei's accounting\nstandardization work, some of Impervious's LN-native communications\nwork, LND's Static Channel Backup system... and I am sure there are many\nmore!\n\nPlease don't hesitate to reach out if you're interested in writing a bLIP\nand want help. We're excited about getting this process going!\n\nAs a reminder, a bLIP is a design document providing information to the\nLightning community, or describing a new feature for the Lightning Network,\nand should provide a concise technical specification of the feature and a\nrationale for the feature. Importantly, if a feature is intended to become\nuniversal or near universal, it must be a BOLT [7].\n\nBecause of this distinction, the bLIP editors do not pass judgment on\nbLIPs, but only monitor bLIP changes, and update bLIP headers as\nappropriate. So long as you check the mailing list to ensure nobody has\nmade a similar proposal before, fill out the required sections specified in\nbLIP-0001, and reserve the required feature bit, message type, or TLV in\nthe bLIP-0002 registry, we are more than happy to merge proposals into the\nrepo.\n\nBest,\nRyan\n\n[1]\nhttps://lists.linuxfoundation.org/pipermail/lightning-dev/2021-June/003086.html\n[2] https://github.com/lightning/blips\n[3] https://github.com/lightning/blips/pull/5\n[4] https://github.com/stakwork/lumo-spec\n[5]\nhttps://github.com/satoshisstream/satoshis.stream/blob/main/TLV_registry.md\n[6]\nhttps://lightning.engineering/posts/2021-11-30-lightning-node-connect-deep-dive/\n[7] https://github.com/lightning/bolts\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211210/2d4236c5/attachment.html\u003e",
"sig": "5e54e871624d92750c15f5a41d6aa4ee3ab49c9bdd49a73da8bf31e77b6ae4bad982529dadd0a246e59584f61118d6b9727dca94210ea42f6f442879b9a81fbb"
}