Quote from: SHIELDcurrency on July 31, 2018, 11:21:42 AM

Quote from: jerry3k5jamiso1 on July 29, 2018, 04:45:45 PM

SHIELD Progress Update

The last few months have been very busy for the SHIELD development team.

Unfortunately, in early April this year, the network of cryptocurrency Verge suffered repeated attacks due to multiple fundamental vulnerabilities. As our codebase was based on theirs, we were vulnerable to the same attack. While we quickly created and deployed a patch to discourage exploiting this specific vulnerability, it became clear that we had to upgrade from the old Bitcoin 0.6.x codebase, to the latest Bitcoin Core 0.16.x, and completely fix those (and potentially other unknown) vulnerabilities.

This forced us to delay our planned roadmap objectives, but we are working hard behind the scenes to complete them as soon as possible.

As for masternodes, Sentinel is a component of recent Dash masternode code which automates governance functions and lays a foundation for their future framework - it doesnt provide any additional functionality on its own. While this may be useful for their purposes, this is not required for SHIELD, and also makes for more complex masternode setup and maintenance. As such, we decided to go with a no-Sentinel approach, which is turning out to be more time-consuming to implement than expected.

And as we are focusing on pushing SHIELD out into the world of crypto, we think it's important to aim for exchanges with higher liquidity, to both raise awareness and make SHIELD easier to obtain for everyone. Weve started work on paperwork, consultations and legal procedures for establishing SHIELD as a company, which large exchanges often require.

SHIELD would like to thank you for your continued support during this busy time.

Thanks for reposting here!

SHIELD does not use race-protocol because it wants to use sentinel?