Crown Development Update 07.07.2020
By: J. Herranz
Tags: Blockchain, Masternodes, Nft, Development, Cryptocurrency

Crown Development Update 07.07.2020

New biweekly format to bring you the latest Crown Platform news

fresh news for a hot summer

In this edition of the Crown development update we bring you the latest news on the NFT Framework, Bitcore, Crown-Electrum and GitLab CI/CD integration tools. Last week we skipped the development meeting and we have moved it to a biweekly rhythm. It adapts better to our current progress and brings more consistent and digested updates.

NFT Framework

Code lead Ashot has continued debugging logs and has located the main issue we have been experiencing lately, which materialises in some nodes freezing on a certain blockheight before new NFT data is written to the chain. This issue is due to inconsistency between blocks / nftoken databases and can be solved levelling out the amount of information contained in each of them before syncing to the network. In order to improve user experience, Ashot is also going to integrate a new -reindex / -resync option starting on the first NFT block instead of at block 0 so that the process will be much faster and easier to complete by affected users. These fixes are estimated to take 1–2 weeks and will be released in a non-mandatory update.

Crown-Electrum

Community developer Ahmedbodi has been working on a new version of the popular lightweight Electrum client. Testing is advanced and Trezor compatibility has been confirmed, although there are still some bugs to iron out when importing previous CRW Trezor key paths. Once everything is working smoothly, the new version will be officially released.

Bitcore / Insight APIs

Developer Zhanzhenzhen has kept up the work on Bitcore and is now integrating the nfproto APIs. Bitcore will be a key piece to develop on the NFT Framework and will be mainly ued to interact with through the Insight APIs. If you are a developer or an entrepreneur looking to use these featuers, feel free to give feedback on the specs you would like them to include.

GitLab Infrastructure and CI / CDs

The infrastructure team is working on the GitLab environment to integrate Electrum to the official Crown Platform repositories and be able to make these processes easier in future. If you want to help out with Docker or have a high level of Python knowledge, feel free to reach out and give a hand.

A Wordpress plugin to create protocols

Recently, contributor Defunctec released a wordpress plugin to create Crown Platform NF-Protocols. It is available on Github:

NFTRegSign methods

Defuncted has also provided a short and understandable explanation of the NFTRegSign modalities available when creating a new NF-Protocol:

1 (SelfSign)

Imagine being the owner of the protocol but anyone can make a token using this protocol. Someone with enough Crown to sign a NFT transaction can use this protocol to create tokens from their wallet, even though they’re not the protocol owner.

2 (SignByCreator)

Owner makes a protocol and only the owners addresses can be used to create tokens. Unlike “SelfSign” only the owner of the protocol can use addresses associated with the protocol wallet, a user for example cannot use their own addresses.

3 (SignPayer)

This allows an outside address to be used to own a NFT but the NFT must be created via the protocol owners wallet. Eg, You own a website, create a protocol with SignPayer. You can then allow users to enter their address as the NFT owner to create and own tokens using your protocol.

Heartbeat Protocol

The heartbeat NF-Protocol has been created by walkjivefly to keep historical data on Masternode and Systemnode coutns. The tokens issued by this protocol every 6 hours can be called upon to visualize historical data on MN/SN counts and can be used by anyone wanting to leverage this information.

That is all for now on the development front. You are invited to join us on Discord if you want to keep track of everything else that is going on.

Thank you for supporting the Crown Platform project!