2 ms·

Pieter's background is in algorithms and cryptography, he's not a networking engineer. The other people you mentioned are solid but their involvement in develop

Pieter's background is in algorithms and cryptography, he's not a networking engineer. The other people you mentioned are solid but their involvement in development is fairly peripheral, with only a handful of commits between them combined. It doesn't take anything away from my argument that bitcoin's netcode is archaic and remains a major hurdle to scaling, and there is way too much political cruft to move things along.

EthanHeilman 9y ago
>It doesn't take anything away from my argument that bitcoin's netcode is archaic and remains a major hurdle to scaling, and there is way too much political cruft to move things along. 1. The Bitcoin-devs rewrote the netcode quiet recently moving from a polling model to an event driven model. 2. Look at all the changes in net_processing [0]. 3. There has been a long term project to refactor and improve the netcode which has been ongoing for several years and has made massive changes to the netcode. How do I know? Over the last two years I have had to rewrite pull requests several times because the netcode has been rapidly changing. [0]: https://github.com/bitcoin/bitcoin/commits/master/src/net_processing.cpp https://github.com/bitcoin/bitcoin/commits/master/src/net_pr...