Skip to content

Instantly share code, notes, and snippets.

@ariard
Created March 26, 2023 20:29
Show Gist options
  • Save ariard/a4e81e6c0f17d71803352774cac8c77c to your computer and use it in GitHub Desktop.
Save ariard/a4e81e6c0f17d71803352774cac8c77c to your computer and use it in GitHub Desktop.

Hi all,

I've been asked by a few people last week what's going on between Chaincode and myself after posting the Jackson Lewis letter. Last Friday, I had Alex Morcos reach out by mail to announce the cancellation of my invitation to the upcoming LN Summit organized by NYDIG in June.

The exchange of emails is available here: https://github.com/ariard/chaincode-improper-communications/blob/master/alex-ln-protocol-developer.pdf https://github.com/ariard/chaincode-improper-communications/blob/master/antoine-ln-protocol-developer.pdf

This is one more element after months of (un)kindness between some folks in the Bitcoin space and myself. While the initial quarrel started from a personal matter, it turns out in the resolution of it I've come to question how some people might use their Bitcoin public status and prerogatives, I believe not always in line with the FOSS standards and beyond. Especially, in the light of how another veteran Bitcoin developer announced a sudden departure from the stage a bit more than a year ago.

Additionally, and after few waves of (non)-objectable gossips whispered on my reputation in the background of the Bitcoin protocol development stage, I prefer to set the matter straight in public, at least from my perspective. I shought many times for mediations and call to rebuild "good faith" communications in private, sometimes more light is what is needed.

Hopefully, in the future we'll have better institutions and processes to solve deontological conflicts between Bitcoin developers.

Disclaimer: my version of the facts. As usual don't trust verify: https://github.com/ariard/chaincode-improper-communications/blob/master/rough-communications.pdf

Amor Fati.

Antoine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment