What exactly have you contributed to Bitcoin code? I'm sure you contributed less than op return nackers such as @Adam Back and @Luke Dashjr. Make it make sense. It seems you and @calle have external motives to be honest. You guys are trying too much and not really addressing the ussue.

Replies (4)

jb55's avatar
jb55 _@jb55.com 3 months ago
I didn't knots people cared about credentialism, but I guess thats fair. so here are mine. there are ~1234 contributors to bitcoin. in terms of raw contributions mine would be 188/1234: https://cdn.jb55.com/s/4104d140cd815d77.txt#:~:text=William%20Casarin If adam has contributed he must be doing it under a nym since I don't see any commits from him. my commits: https://cdn.jb55.com/s/8b84ea34bec4caac.txt I worked on usdt tracing and performance optimizations. I am by no means a frequent contributor, I mainly work on lightning tech. things I've worked on: core-lightning: https://cdn.jb55.com/s/283cc3006988b7b4.txt lnsocket - a C/rust library for talking to lightning network nodes btcs - a bitcoin toy bitcoin script interpreter bitcointap - A tool for tapping into bitcoin-core tracepoints to extract data in realtime: opentimestamps: i put together the haskell implementation of ots, and built a suite of tools that work with them: I maintain the "bitcoin" nodejs rpc lib: https://npmrepo.com/bitcoin I've hacked on HWI and helped with a lot of the bitcoin-nix infrastructure. I've also been around since 2010 and have a decent understanding how various parts of the codebase work, especially on the script side. what about you?
Mr. Back's work is in the citations of the whitepaper and Luke got way more credentials, so do the other nackers who are in the top rows. I, unfortunately, only started on this journey in 2017, but I am constantly learning. I try to remain unbiased and wrote about the issue my thoughts. More nuanced approach would be appreciated if you are with the ackers.