/biz/ - Business & Finance

>>50433192
A reflection on the state of the Monero Project source code.

One of the positives of the Monero Project compared to the Bitcoin Project is that the former has not undergone a definitive ossification process, which allows Monero to enjoy new developments in the cryptography branch among other performance optimisations in its code.
But this is a double-edged sword. While Monero keeps up with the eternal cat-and-mouse fight for privacy, it also means that with every modification to the code there is a non-zero chance that we are introducing catastrophic bugs into it.
Of course the argument is that there is enough crowdsourcing money to pay for source code audits, however I don't believe that's enough, not in the least. In fact a quick look at the Monero Project's Github indicates that there are very few people participating in its development in any way. This number is even smaller if you consider the core developers, which is basically programmed by a single person.

Within all the random and unsubstantiated FUDs about Monero that are spread around the internet, this is the least publicised and I believe the closest to reality in the sense that there could be a destructive impact on the network. When you see people commenting on the FUD of "constant hard forks" they are usually mentioning the fight against ASICs, which has already been solved with RandomX. I am more interested in the possibility of introducing new bugs in the source code.

My conclusion is that there is an absurd and extremely serious lack of talent in the Monero project. This project needs a much larger number of contributors both in the matter of C++ development and in the mathematical and cryptographic part (Monero Research Lab).
What would be achievable and practical tasks to fix this problem in the Monero project?