3 ms·

"nor do they recognise the importance of having robust netcode" Refactoring of the core networking code has been ongoing for quite some time. See https://githu

"nor do they recognise the importance of having robust netcode" Refactoring of the core networking code has been ongoing for quite some time. See https://github.com/bitcoin/bitcoin/projects/4 https://github.com/bitcoin/bitcoin/projects/4. "Can you name anybody with a good background in networking? You can't point to a list of 100 odd names and assert that certain skills must be present" sipa? He worked as an SRE at Google before starting work on bitcoin. [1] rustyrussell? He has done extensive work on the linux kernels networking subsystems. [2] cdecker? He did a phd at the Distributed Computing Group in Zurich which included work on scaling bitcoin. [3] gwillen? Also a SRE at Google before bitcoin, and worked on Dapper[1]. [1] https://www.linkedin.com/in/pieterwuille https://www.linkedin.com/in/pieterwuille [2] https://en.wikipedia.org/wiki/Rusty_Russell https://en.wikipedia.org/wiki/Rusty_Russell [3] https://disco.ethz.ch/alumni/cdecker https://disco.ethz.ch/alumni/cdecker [4] https://static.googleusercontent.com/media/research.google.com/en//archive/papers/dapper-2010-1.pdf https://static.googleusercontent.com/media/research.google.c...

Laforet 9y ago
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...

Laforet 9y ago

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...