No need to apologize! Perhaps this confusion shows that the current process
surrounding creating/modifying/drafting BOLT documents does indeed need to
be better documented. We've more or less been rolling along with a pretty
minimal process among the various implementations which I'd say has worked
Sorry did not realized that BOLTs are the equivalent - and aparently many
people I spoke to also didn't realize that.
I thought BOLT is the protocol specification and the bolts are just the
sections. And the BOLT should be updated to a new version.
Also I suggested that this should take place for
We already have the equiv of improvement proposals: BOLTs. Historically new
standardization documents are proposed initially as issues or PR's when
ultimately accepted. Why do we need another repo?
On Sun, Jul 22, 2018, 6:45 AM René Pickhardt via Lightning-dev <
lightning-dev@lists.linuxfoundation
Lightning is covered by BIPs already. There's no need for a separate
repository, and the existing BOLTs should be submitted to the BIPs repository
too.
On Sunday 22 July 2018 13:45:21 René Pickhardt via Lightning-dev wrote:
> Hey everyone,
>
> in the grand tradition of BIPs I propose that we als
Hey everyone,
in the grand tradition of BIPs I propose that we also start to have our own
LIPs (Lightning Network Improvement proposals)
I think they should be placed on the github.com/lightning account in a repo
called lips (or within the lightning rfc repo) until that will happen I
created a dr