Recommended v0.14.0.1 upgrade
Fixing the Emerald NFT glitch
The NFT framework activated as planned on 24 March but due to an unfortunate oversight, token protocols could not be registered. This was due to a configuration difference between testnet and mainnet. Artem has worked out a fix which can be effected without a mandatory update or protocol change (which could have proved expensive with exchanges). Testing was quite a difficult operation but was completed successfully last week.
Consequently we have released v0.14.0.1 which is a recommended, non-mandatory, upgrade. We encourage all node owners to upgrade their nodes and anyone who wants to register NFT protocols or tokens to upgrade their wallet. The first protocols and tokens have now been successfully registered.
No restart required for MN/SN
We’re sorry to have to ask you to upgrade again so soon but it’s a simple process and one you could do this weekend in just a few minutes. There is no protocol upgrade so there should be no need to issue start-alias commands for your updated nodes.
Windows and Mac users
QT wallets will prompt automatically to download the upgrade next time they are started. The upgrade procedure is the same as for the previous Emerald update:
- Download the Windows 64-bit or MacOS or MacOS DMG update.
- Shutdown the wallet.
- Open the downloaded update. This will unzip it into a directory in your downloads folder. Navigate to the Crown-v0.14.0.1-Emerald\bin folder.
- Copy the executables over the old ones.
- Restart the wallet.
Linux users
For masternodes, systemnodes and linux wallets the one line script to do all of the above is
sudo curl -s https://gitlab.crownplatform.com/crown/crown-core/raw/master/scripts/crown-server-install.sh | bash -s
Why should I upgrade again?
Every upgraded node or wallet will help speed up the registration of protocols and tokens. Nodes which do not upgrade will slow down NFT protocol and token registrations because they cannot mint a block containing one. Instead any registration transactions will sit in the mempool of v0.14.0.1 nodes until one of those mints a block. If all nodes upgrade then the NFT protocol or token registration delay will usually be one block or about one minute. If half the nodes upgrade the average delay will be about two minutes (although it could be longer).
