Closed ariard closed 1 month ago
TheBlueMatt
commented
1 month ago This issue tracker is for issues related to the development of the lightning protocol, ideas for the lightning protocol, and notices to lightning developers about relevant upcoming events. If you want to discuss the invite list that I built for a previous event, you're welcome to send me an email.
ariard
commented
1 month ago I think what you're depecting is misleading as in the past Github communication channels were also used to discuss meaningful disagreement among lightning developers about the philosophy of the lightning protocol development, e.g the spin-off of the blip effort. See PR #884 for a compelling example.
On the present issue, I asked you questions on an event directly concerning the open-source development of the protocol. I.e the technical criteria on which people have been invited and how many people were invited to this event. I'm not asking any personal information, so I don't see why this topic should be talk off-the record. I'm staying fully available if you wish to engage on this topic on this present issue tracker, the mailing list or IRC, as long as it’s in public.
Beyond, for an invitation to talk about this topic in private by email, I find this dubious. May I recall from public information that almost 10 years you were one of the co-founder of Blockstream, raise $$$ for a whitepaper with grandiose publicity, and then you quit this company after a ~1 year of working there, without apparently paying back your business commitments towards your VCs and other financial investors to deliver a financial return. So your “commercial morality" can be legitimately questioned.
And I'm not sure as of today, you have any open-source protection in you're work employment with block inc. I.e guaranteeing that you can conduct yourself with margins of autonomy in matters of bitcoin open-source, e.g contributing to the development of the lightning protocol freely, or that you should take care first of fulfilling your fiduciary duty towards block inc as an employee.
All that said, I'm still open to be communicated private information about the role you said to have played in the organization of the last so-called Lightning Dev Summit, by the intermediary of our respective legal representative. One of my lawyer can listen to what you have to said about this Lightning Dev Summit, and clear any currently standing misunderstanding.
@TheBlueMatt
https://github.com/lightning/bolts/issues/1171#issuecomment-2391532275
"people who actively contributed to the spec (or were invited by a major lightning implementation cause they regularly work on it) or were otherwise at the last one"
Thanks Matthew Corallo for taking the individual responsbility to constitute the invitation, but I'm not satisfied with your answer.
I've been disagreably surprised to not have been invited to this edition of the Lightning Dev Summit. Despite years of contributions of this specfication (and still reviewing broken ideas about lightning, when they show up on usual public communication channels), and have being invited by Caralie Chrisco at the last Lightning Dev Summit in date of the 31 January 2023.
If you can give more details on the technical criterias and how you define them in a neutral, consistent and with blight lines, on which you consisted this invitation list, to avoid misunderstanding in the future. I don't wish to freely accuse your employer Block Inc (cc @jackjack) of doing a slow corporate capture of the lightning protocol a la Microsoft (after all it's a NYSE trade company with commercial profit as a fiduciary duty towards the stakeholders), but external observers can have more than a reasonable doubt.
More coldly, I've also surprised to have not found any work or discussions in the transcript made available of this lightning summit of the mass force-closure of lightning channels, crashing on-chain at the same time. A problem widely described in the Lightning paper by Joseph Poon and Tadge Dryja under the "9.2 - Forced Expiration Spam". That technical problem characerizes a long-term system risk for the lightning ecosystem, and a scalability issue. With more and more off-chain channels being opened, and all of them hitting the blockchain at the same time for a scarce blockspace, there could be some major loss of funds. That problem was discussed during the Lightning Dev summit of 2022 if my memory is correct, and some other folks agree on its seriousness.