Why
Currently, Monero only has one node written in C/C++, many would see this as an issue. Having only one implementation makes us more vulnerable to implementation bugs, having another node will help us to spot and fix these issues.
monerod’s code is also a bit of a mess, as many devs who have worked on it would agree. Cuprate is a fresh start and is built with modularity in mind which will lead to a cleaner and easier to understand codebase.
Having a consensus rules document will make it easier for developers to build software to interact with Monero. It will also make it easier to spot potential issues with consensus rules.
Thank you for the write-up, I really appreciate it. You make some excellent points. Consider bringing this up in the CCS proposal discussion.
This Licence decision diagram might be helpful for general public:
- Allow others to create closed-source projects with your code?
- Yes -> MIT license
- No -> Allow others to create a closed-source web service with your code?
- [3.] Yes -> GPL-3 or LGPL-3
- [3.] No -> AGPL-3
