https://medium.com/crownplatform/crown-development-meeting-minutes-04-05-2020-58c082db9eb6

Crown development meeting minutes 04/05/2020
Just the facts, ma’am

Present: crowncoin-knight, Crownfan, pjcltd, walkjivefly

Ashot couldn’t make the meeting but afterwards sent a very short report saying he is still working on the NFT integration and expects it to take about another two weeks. He also provided a link to the essential barebones NFT transaction structure which has now been passed on to the Bitcore and Electrum developers.

There is no progress on the NFT trading design specification documentation.

Community developer Zhen is still working on the Bitcore NFT adaptation. He asked for a brief requirements specification. Our minimum requirements are:
    * correctly decodes NFT transactions
    * it can be used to register both NFT protocols and NF tokens.

    crowncoin-knight will check with Farid of Chronovault what else he requires from it.

Our “on loan” MUE engineer is trying to get ElectrumX to sync and is currently stuck at the first block with NFT transactions. There may be as yet undiscovered NFT-related issues in the Electrum-Crown wallet code as well.
   
Crownfan has been testing PolisPay. The integration is not quite complete yet but hopefully will be released this week.

walkjivefly has added dedicated competition and CRWcard pages to the Platform Monitor, and added geolocation, country totals and map display to the masternode and systemnode pages.

A number of users are experiencing block validation errors on some blocks containing NFT transactions. Their node or wallet ends up banning all of its peers and/or being banned by all of its peers and is then stuck, unable to do anything. This only happens to a small number of users on a small number of blocks. The symptoms are “well known”, the underlying reason is not. Ideally, we need Artem to investigate since Ashot has not had time to do so. Unfortunately, despite there having been at least seven occurrences we know of, most victims have not been uploading their debug.logs as requested so we have very little documentation for Artem/Ashot to work from. The problem does not reproduce at will which makes debugging it much harder.