š
Original date posted:2015-10-26
š Original message:
Hey everybody,
I created a new OSS-organisation on GitHub lightning-core and opened a
new repository dedicated to hold the specifications of any lightning
node.
https://github.com/lightning-core/lightning
This has several positive effects:
(1)
I am positive this will help to ensure we all build somewhat
compatible software. As we all only come together every once and again
on IRC (and rarely on the mailing list), we end up building the same
things in parallel that are not compatible at the end of the day.
While it is great to have implementations in different languages for
different systems, would be even better if they end up being one large
network at the end of the day.
(2)
It is in general a good idea to have the product specifications and
implementations in separate repositories. This way we have the
contract each implementation has to abide separate and clear in view.
(3)
It is easier to work towards different targets that may seem out of
reach right now, but still have them structurally on the same
repository. If some guy decides to work on an implementation on some
advanced topic, he will have a difficult time getting it across on the
mailing list. I think a github repo is a much better place to share
these ideas.
(4)
Anyone doing a complete new implementation does not have to search
across different implementations and mailing list posts to find
answers how his software should behave to communicate with the
network. The specification will be a great guideline for new
implementations
As I just started it, practically everything is still missing. I
started writing together the current implementation on the encryption
layer, but even there I noticed how much of it I have to scramble
together from different sources.
Feel free to fork and write up, we can always discuss the status quo
before pushing it to master. The skeleton is missing a lot too, but we
have to start at some point...
Cheers
Mats
Mats Jerratsch [ARCHIVE] /
npub1hzā¦q5x8w
2023-06-09 12:44:58
in reply to nevent1qā¦9w2p
Author Public Key
npub1hz386xq4qszumlx5fsxa3kuxpaf8qvfrqqjg8zdl2l892hrcg55q6q5x8wPublished at
2023-06-09 12:44:58Event JSON
{
"id": "4d4e7bae27483a5d0697e864eaa91156fb79d3718fe6c767a99c6b0fbb66df96",
"pubkey": "b8a27d18150405cdfcd44c0dd8db860f5270312300248389bf57ce555c784528",
"created_at": 1686314698,
"kind": 1,
"tags": [
[
"e",
"517a92e9aa5efb506b0818c6ee935ab1cec59756ee75153c91552d59ee89ffea",
"",
"reply"
],
[
"p",
"9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c"
]
],
"content": "š
Original date posted:2015-10-26\nš Original message:\nHey everybody,\n\nI created a new OSS-organisation on GitHub lightning-core and opened a\nnew repository dedicated to hold the specifications of any lightning\nnode.\n\nhttps://github.com/lightning-core/lightning\n\nThis has several positive effects:\n\n(1)\nI am positive this will help to ensure we all build somewhat\ncompatible software. As we all only come together every once and again\non IRC (and rarely on the mailing list), we end up building the same\nthings in parallel that are not compatible at the end of the day.\nWhile it is great to have implementations in different languages for\ndifferent systems, would be even better if they end up being one large\nnetwork at the end of the day.\n\n(2)\nIt is in general a good idea to have the product specifications and\nimplementations in separate repositories. This way we have the\ncontract each implementation has to abide separate and clear in view.\n\n(3)\nIt is easier to work towards different targets that may seem out of\nreach right now, but still have them structurally on the same\nrepository. If some guy decides to work on an implementation on some\nadvanced topic, he will have a difficult time getting it across on the\nmailing list. I think a github repo is a much better place to share\nthese ideas.\n\n(4)\nAnyone doing a complete new implementation does not have to search\nacross different implementations and mailing list posts to find\nanswers how his software should behave to communicate with the\nnetwork. The specification will be a great guideline for new\nimplementations\n\n\nAs I just started it, practically everything is still missing. I\nstarted writing together the current implementation on the encryption\nlayer, but even there I noticed how much of it I have to scramble\ntogether from different sources.\n\nFeel free to fork and write up, we can always discuss the status quo\nbefore pushing it to master. The skeleton is missing a lot too, but we\nhave to start at some point...\n\nCheers\nMats",
"sig": "f39531a8a7e9a0f821711f67a64beca9b76532db24d3dd5e505e8f43da2cb5a6cfa48081783b0018e672e16c9e245c6ac8cf1e11efda4d9b14e205feefb59bf9"
}