Quote from: imd1 on December 02, 2015, 10:03:53 AM

Quote from: crypti PR on November 26, 2015, 01:25:44 PM

Crypti: Delegate & Developer Edition v0.5.3

Hello Everyone,

We are happy to announce the release of Crypti: Delegate & Developer Edition v0.5.3.

Todays incremental update, resolves two issues found in the previous release: v0.5.2. One of the problems was a small syncing bug, which occurred under rare circumstances. The other problem, resulted in an empty public key field for certain Crypti accounts. Therefore, with todays release, these two issues have now been resolved.

All delegates are asked to update as soon as possible.

Coinciding with todays release, comes new pre-built binary packages for multiple architectures and platforms. The new installation process provides a simple download, unpack and run scenario for the following platforms:

Linux (x86_64)
Linux (i686)
Mac OS X (x86_64)
FreeBSD (x86_64)
Further support for other platforms (such as ARMv6, ARMv7), will be added soon.

Please read Installing Crypti (from Binaries) for instructions on how to select your platform and install.

As a reminder, we still have the following alternative installation options:

- Docker Image
- Using CryptiKit
- From Source

Remember! Crypti v0.5.2 (Lite client) does not need to be updated, as it simply connects to the delegate nodes on the network, and remains API compatible with todays release.

Thank you very much!

Blog Post

Hi Max,

I've a query - you posted here that all delegates should be updated to v0.5.3 as soon as possible.

I saw this post today and have not updated my delegate yet but I can see it is forging fine - same applies to many active delegates, why so?

Crypti v0.5.3 is no hard fork so it's still working. However, we fixed some bugs in the version and we recommend to update. Else it can happen that your node is spreading the mistakes though the network. In this case the mistake would be that some accounts don't have a public key, which results in quite a few problems as you can imagine.

This bug was very rare, that's why we didn't encounter it for a long time. At one point it will happen and will cause this ugly bug. That's why we are asked all delegates to update as soon as possible.