Quote from: cryptrol on August 15, 2017, 04:35:01 PM

No, heartbleed and posterior bugs.
You can restrict RPC to local access but having the bug in there is kinda creepy ...

Hi cryptrol,

Well honestly, the heartbleed bugs only are a problem if you didn't compile your own wallet.
My node is running OpenSSL v1.0.2l and hence is not affected by heartbleed.

Who leaves RPC open in the wild anyway without a tcp-wrapper or iptables?

You bring up a legitimate point and the solution is simply compiling the builds linked to a new version of OpenSSL.

I'd have figured you were referring to BIP66.

Much of the "maintenance" can be had by rebasing.
At that time, new improvements will be inherited and modern binaries may be distributed.

If anybody is looking for a blockchain to store data; it makes sense to find one which has survived a few years... otherwise what is the point?
This chain is 1.8G and hasn't been spammed to death and has utility in multiple applications.
ByteSt@mp is a testament to innovation secured with a chain of blocks.

If you found Datacoin today and it had a 500G blockchain, would you so easily dismiss it?

What else did you find aside from an SSL linking problem only affecting those who don't compile their own wallet?

Best Regards,
-Chicago