📅 Original date posted:2016-03-17
📝 Original message:
Anthony Towns <aj at erisian.com.au> writes:
> Hello lightning implementors!
>
> (Posted to lightning-dev as well, hopefully that's fine with everyone)
>
> Matsjj set up a repo a while ago for collaborating on documenting the
> lightning protocol and gave a bunch of us admin access:
>
> - https://github.com/lightning-core/lightning
>
> """I think it is a very good idea to carry all the different
> implementations to one spot. I think such a repository is best suited
> for it."""
>
> - https://github.com/lightning-core/lightning/pull/4#issuecomment-151778273
>
> I think the layout is a bit too nested (which makes sense coming from
> the Java implementor, I guess? :) and I think it'd be good to have a
> simple way to decide how to move ideas into/through the repo, without
> making it a place where there's any point trying to politicise proposals.
> (It's kind of telling that something's wrong when even matsjj hasn't
> been able to get his pull requests accepted :)
>
> Anyway I've taken Rusty's couple of BOLT proposals as well as the shachain
> design txt and rearranged them in a way I think makes sense:
>
> - https://github.com/ajtowns/lightning-core/tree/rusty
>
> What do you guys think?
>
> I hear there's totally going to be released code out by
> northern-hemisphere summer, so documenting the protocols/standards is
> only going to get more pressing...
>
> My inclination is to add:
>
> - matsjj's pull requests [0]
> - the anonymous "R", via private key reveal stuff [1]
> - Joseph's 2-of-3 Instant Escrow [2]
>
> as additional "early drafts". Probably things from Rusty's "Deployable
> Lightning" paper (like the HTLC scripts), or the "elkrem" scheme, or
> Nicholas Dorier's "backward deterministic [revocation] Value" stuff
> would be good too...
FWIW, my rough plan was BOLT #3 was going to be the transaction formats,
and BOLT #4 the onion and failure message formats (as portended in BOLT
#2's references).
Cheers,
Rusty.
Rusty Russell [ARCHIVE] /
npub1zw…hkhpx
2023-06-09 12:46:01
in reply to nevent1q…jsh3
Author Public Key
npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpxPublished at
2023-06-09 12:46:01Event JSON
{
"id": "b414b2213d42ab73b03392aaad3acfe01a000d0d0a00c2bb6fdf242a08511e42",
"pubkey": "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425",
"created_at": 1686314761,
"kind": 1,
"tags": [
[
"e",
"512c06ae0143512f49e5abf274ed72851bc5aa8be8c43678fcbc207d10566de1",
"",
"root"
],
[
"e",
"8f9674ea800a2d374d722362ed70514d7f33b0e0880ab02555574a479f3aabc3",
"",
"reply"
],
[
"p",
"f0feda6ad58ea9f486e469f87b3b9996494363a26982b864667c5d8acb0542ab"
]
],
"content": "📅 Original date posted:2016-03-17\n📝 Original message:\nAnthony Towns \u003caj at erisian.com.au\u003e writes:\n\u003e Hello lightning implementors!\n\u003e\n\u003e (Posted to lightning-dev as well, hopefully that's fine with everyone)\n\u003e\n\u003e Matsjj set up a repo a while ago for collaborating on documenting the\n\u003e lightning protocol and gave a bunch of us admin access:\n\u003e\n\u003e - https://github.com/lightning-core/lightning\n\u003e\n\u003e \"\"\"I think it is a very good idea to carry all the different\n\u003e implementations to one spot. I think such a repository is best suited\n\u003e for it.\"\"\"\n\u003e\n\u003e - https://github.com/lightning-core/lightning/pull/4#issuecomment-151778273\n\u003e\n\u003e I think the layout is a bit too nested (which makes sense coming from\n\u003e the Java implementor, I guess? :) and I think it'd be good to have a\n\u003e simple way to decide how to move ideas into/through the repo, without\n\u003e making it a place where there's any point trying to politicise proposals.\n\u003e (It's kind of telling that something's wrong when even matsjj hasn't\n\u003e been able to get his pull requests accepted :)\n\u003e\n\u003e Anyway I've taken Rusty's couple of BOLT proposals as well as the shachain\n\u003e design txt and rearranged them in a way I think makes sense:\n\u003e\n\u003e - https://github.com/ajtowns/lightning-core/tree/rusty\n\u003e\n\u003e What do you guys think?\n\u003e\n\u003e I hear there's totally going to be released code out by\n\u003e northern-hemisphere summer, so documenting the protocols/standards is\n\u003e only going to get more pressing...\n\u003e\n\u003e My inclination is to add:\n\u003e\n\u003e - matsjj's pull requests [0]\n\u003e - the anonymous \"R\", via private key reveal stuff [1]\n\u003e - Joseph's 2-of-3 Instant Escrow [2]\n\u003e\n\u003e as additional \"early drafts\". Probably things from Rusty's \"Deployable\n\u003e Lightning\" paper (like the HTLC scripts), or the \"elkrem\" scheme, or\n\u003e Nicholas Dorier's \"backward deterministic [revocation] Value\" stuff\n\u003e would be good too...\n\nFWIW, my rough plan was BOLT #3 was going to be the transaction formats,\nand BOLT #4 the onion and failure message formats (as portended in BOLT\n#2's references).\n\nCheers,\nRusty.",
"sig": "1e6dbf1f0ad7fb120fcdb85c9c84ca083b209c28734e0fddb7f1cc7c07d0cca555639e541e7557c559596f93bd6d9449a038b6bc70d741486906c62f61fb11ce"
}