Crown development meeting minutes 28/11/2019
Just the facts, ma’am
Present: Artem, Ashot, crowncoin-knight, walkjivefly
- Artem has finished the local database structure. He’s finalising the API calls to the core implementation. There were no commits this week but he hopes to push his latest changes soon. These will increase the protocols registration component to about 90%. Based on already committed code, the NFT percentage completion numbers are currently
* NFT Core — 100%
* NFT Registration — 100%
* NFT Protocols Registration — 85%
* Bitcore NFT support for web-development — 40%
- Ashot has a bunch of commits waiting in the wings but has not pushed them yet because the code doesn’t currently build. He encountered some problems with the main Makefile and after fixing them is back to compilation errors related to masternodes, systemnodes and instantsend. Problems like this were expected from the outset so we should not be discouraged. Nothing is ready for testnet yet.
- walkjivefly and defunctec made a pass through the Gitlab and Github open issues and closed a good number of them. walkjivefly made and closed some merge requests in Gitlab. defunctec has mirrored Gitlab open issues in Github to increase their accessibility to the wider community.
- crowncoin-knight asked Artem and Ashot to please commit whatever changes they make as soon as possible. Flipside Crypto are fully integrating our metrics into their Crown rating now and developer behaviour is a big component of that. In the last couple of weeks our rating has improved considerably. The biggest area of improvement was development as shown in the dashboard screenshots below. We hope to have a conference call with Flipside Crypto next week to discuss updates to the dashboard to include on-chain metrics. Unfortunately it probably won’t happen before the next development meeting so won’t be reported in the minutes. walkjivefly may create a standalone Medium article about it instead.
- Infrastructure have requested a non-mandatory wallet release to update the seed node IP addresses so that we can remove the need to pay for expensive Digital Ocean servers by credit card each month. Ashot said this would require a disproportionate development effort and wants to wait until we’re ready to push the Emerald release. Consequently we will operate with just three seed nodes until there is a planned release. This may degrade initial syncing progress for nodes syncing from scratch over the network. Users are advised to use the bootstrap if they encounter syncing problems.