please also a note to all to update to the most recent version of forknote v2.0.1.1 link is provided in first post.
https://github.com/forknote/forknote/releasesLinks to most update version for every system can be found here
Which version of forknote is it that you refer to here
What I mean is that when you start the forknote daemon, just before it connects to the nodes, you can see the version in the top right. This version for NNC was 2.0.1.1221 for the last while.
Without going through the effort to download the wallets again, can you confirm if the wallets you asked people to upgrade to is still 2.0.1.1221 or did you make a later version?
The link to latest released is v2.0.1.1 which was just updated 15days ago with 41 addition and 10 code deletions directly related to the Monero big fix. We have have scanned out network to ensure it is big free and further consulted with outside experts to make sure we have made all precautions to provide a pure block chain without the double spending which was found on ByteCoin and forked version being created such as DashCoin. Our download links will now point directly to Forknote.net so all user are able to establish a high level of trust rather than linking to a mega.nz link or our website.
I see now what happened.
When forknote was updated on May 9, they did not update the build number. The build number remained 1221 (
https://github.com/forknote/forknote/blob/master/src/version.h.in) I am sure this was an oversight as it makes it more complex to distinguish between builds.
I can see that NicNac is using the latest build that includes the security fix, but to confirm users must check the hashes of their binaries. The forknoted binary hash can be checked at
https://www.virustotal.com/en/file/e0f5303c1c048d65c2b107316cdcfbfce2b2a5fbec595753c61d571033fccfab/analysis/ Just download the latest forknote binaries from the forknote github, upload the forknoted to virustotal and compare the hash. The sha256 hash is e0f5303c1c048d65c2b107316cdcfbfce2b2a5fbec595753c61d571033fccfab.
Also check the hash of the current binary you are using and if it is different, download the latest one and create a new folder for your binaries and also download the config file from OP and place in the configs folder.
You can check the hash of the previous forknote binary on virustotal at
https://www.virustotal.com/en/file/a263005df57c2365989d785b20f25ed0aeab0ba933ccb1a0dc5fa84610911009/analysis/ The sha256 hash of the previous binary was a263005df57c2365989d785b20f25ed0aeab0ba933ccb1a0dc5fa84610911009
