In case anyone has been following, a semi-critical architecture dependent signature exploit has been found that can cause the chains of many cryptocurrencies to fork. I learned of this exploit only two or three days ago and have been researching it and determining the best fix, which seems to come from Peercoin.

I have updated github with the fix to this exploit and have been running tests.

https://github.com/StealthSend/Stealth/commit/e18175fe125b196d9bb1f25d3234f7eef3759b9f

In addition to patching this exploit, I fixed some longstanding synchronization issues, which I will be testing over the next couple of days.

https://github.com/StealthSend/Stealth/commit/540f745c4924f0c98661bf0cfeac85fbc48e8533

I will have new builds available within a day, but they may not be signed by CryptoCertify. Since release is timely, I won't wait on the code signatures. As soon as the signed builds are available, I'll replace the unsigned builds with the signed builds. This could take as long as 5 days. The issue with CryptoCertify code signing is my own mistake. I did not know I needed to manually approve the signing cert after it was re-issued. Because I missed the window of approval, I had to restart the issuance process. It may take several days before I can approve the cert and sign the builds.

When syncronization testing is done, I will issue an alert so that block explorers and exchanges update to the new sources (version 2.0.2.0). This alert will be issued within a day.

A description of the forking bug can be found here:

https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009697.html
https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki


-- Hondo