Crown development meeting minutes 22/06/2020

Just the facts, ma’am

Present: ashot, crowncoin-knight, Crownfan, walkjivefly

1. Ashot has been researching the NFT-glitch. After adding a lot of additional diagnostics he has not managed to reproduce the problem again, but does have a theory about how the error arises. If the theory is correct it’s not something that can be reproduced on demand. He will continue working on it.
2. Ashot will attempt to resolve the NFT-glitch before investigating the Dash/zerocoin masternode improvements.
3. Community developer Zhen reported he’s implemented most of the Bitcore nftoken command. The nftoken list subcommand is causing some problems because of its variable arguments which is not something Bitcore usually deals with.
4. The latest Electrum wallet connection problem is due to a protocol version mismatch. The old Crown-Electrum wallet used protocol version 1.1 but the ElectrumX server now uses version 1.5. The old wallet had a number of patches making it Crown specific. The developer recommends rebasing it on the current Electrum wallet and re-applying the Crown customisations. Fortunately he is already working on a multi-coin Electrum version. He has offered to include Crown customisation in the new wallet at no extra charge so long as there are no insurmountable obstacles.
5. Artem has not had any time to spend on the NFT trading design specification documentation.
6. defunctec has created an NFT proposal generator plugin for Wordpress. It’s a sister-application to the NFT generator he released last month.
7. We will be making two development bounty payments from the community sweeper fund to the contributors working on the nftree carbon offsetting application. Hopefully by the end of July we will have secured the funding needed to be able to formally launch the bounty program alluded to last December.