Versioning scheme
What is the versioning scheme of Cuprate ? I see three options:
- Semantic Versioning: MAJOR.MINOR.PATCH with first release of Cuprate being 1.0.0
- Semantic Versioning: MAJOR.MINOR.PATCH but following monerod versioning. So Cuprate first version will likely be 18.3.1
- 0ver versioning: 0.MINOR.PATCH. I don't see any reason to use this.

Pros of following monerod versioning:
- Same version means it is compatible by network consensus.
- Easier for people to understand the latest version
Cons of following monerod versioning:
- Doesn't make a lot of sense to come out with an Alpha software at version 18.
- How do we name our fixes release ? We shouldn't be limited by monerod number of updates. Maybe MAJOR.MINOR.PATCH-N (eg. 18.3.1-5)