📅 Original date posted:2019-06-27
📝 Original message:
Hi all,
We recently proposed a standard for encrypting data with the pre-image that
is being revealed over Lightning[1]. After talking with various folks in
the ecosystem the consesus seems to be it would be a good idea to create a
repository for organizing LAS (Lightning Application Standards)[2]. The
hope here is that we can start building standards so that Lightning app
developers can design their LAPPs to be compatible with other LAPPs. This
should also make it easier for wallet developers to hook into different
LAPPs with a standard.
If this idea gains momentum, I think LAS's should be kept separate from the
BOLTs. BOLTs should define low level Lightning protocol where it is
_imperative_ that Lightning implementations comply to the BOLT standards. I
think LAS's are more of "suggestions" to make it easier for everyone to
communicate and interact with each other in a standardized way. This also
encourages the idea of segregating "backbone" implementations of the
Lightning network with higher level wallet software. This makes it easier
to distinguish what useful things library developers might want to support
vs what BOLT compliant implementations need to support. Perhaps for
pragmatic reasons for now we would just reuse the current lightning-rfc
repo[3].
In my opinion, BOLT11 could be thought of as a LAS as it does not talk
about the actual Lightning protocol, but rather a canonical way to encode
information about the protocol to end users (similar to bitcoin addresses).
-Chris
[1] -
https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-June/002035.html
[2] -
https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-June/002046.html
[3] - https://github.com/lightningnetwork/lightning-rfc/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20190627/ac1d8972/attachment.html>;
Chris Stewart [ARCHIVE] /
npub1u0…dnn03
2023-06-09 12:55:22
in reply to nevent1q…v39w
Author Public Key
npub1u03cz099kt69z9awg232rjvlt34azukpzkkvy5uqv64dj9j5fqtshdnn03Published at
2023-06-09 12:55:22Event JSON
{
"id": "864830bde55b65760bc2253f57f3ae000dabff3706292e86d464988602bef479",
"pubkey": "e3e3813ca5b2f45117ae42a2a1c99f5c6bd172c115acc2538066aad916544817",
"created_at": 1686315322,
"kind": 1,
"tags": [
[
"e",
"c9e7480d074f72f6f91f5670bf29dd4b157eca8c2e62b819be9a63e84b824011",
"",
"reply"
],
[
"p",
"9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c"
]
],
"content": "📅 Original date posted:2019-06-27\n📝 Original message:\nHi all,\n\nWe recently proposed a standard for encrypting data with the pre-image that\nis being revealed over Lightning[1]. After talking with various folks in\nthe ecosystem the consesus seems to be it would be a good idea to create a\nrepository for organizing LAS (Lightning Application Standards)[2]. The\nhope here is that we can start building standards so that Lightning app\ndevelopers can design their LAPPs to be compatible with other LAPPs. This\nshould also make it easier for wallet developers to hook into different\nLAPPs with a standard.\n\nIf this idea gains momentum, I think LAS's should be kept separate from the\nBOLTs. BOLTs should define low level Lightning protocol where it is\n_imperative_ that Lightning implementations comply to the BOLT standards. I\nthink LAS's are more of \"suggestions\" to make it easier for everyone to\ncommunicate and interact with each other in a standardized way. This also\nencourages the idea of segregating \"backbone\" implementations of the\nLightning network with higher level wallet software. This makes it easier\nto distinguish what useful things library developers might want to support\nvs what BOLT compliant implementations need to support. Perhaps for\npragmatic reasons for now we would just reuse the current lightning-rfc\nrepo[3].\n\nIn my opinion, BOLT11 could be thought of as a LAS as it does not talk\nabout the actual Lightning protocol, but rather a canonical way to encode\ninformation about the protocol to end users (similar to bitcoin addresses).\n\n-Chris\n\n[1] -\nhttps://lists.linuxfoundation.org/pipermail/lightning-dev/2019-June/002035.html\n[2] -\nhttps://lists.linuxfoundation.org/pipermail/lightning-dev/2019-June/002046.html\n[3] - https://github.com/lightningnetwork/lightning-rfc/\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20190627/ac1d8972/attachment.html\u003e",
"sig": "8f00e8f37dd7e61dad41f970513d001627e7dbdb873f252b9259ba9dc6dfe2b273ecec0cb4632003fe1505720f226e4ff5fbe854eff9b5c217e87a823dd79af8"
}