Quote from: Evil-Knievel on January 25, 2017, 07:43:31 AM

Quote from: ImI on January 25, 2017, 02:28:43 AM

Quote from: Evil-Knievel on January 24, 2017, 10:15:53 PM

Quote from: coralreefer on January 24, 2017, 10:12:04 PM

EK, can you please clarify if this proposal is just for the validation of ElasticPL submissions / solutions. The blockchain would still be secured by POS, right?

Exactly, supernodes would be only responsible for work related stuff.

Question: How easy would it be to implement supernodes at a later stage? I guess we would need a hardfork right? Another thing is security. Supernodes could cause security risks like DDOS on those few supernodes or some other nasty stuff. (Dash should have theoretically the same issue with their masternodes.)

At a later stage a hardfork would be required.
I have been brainstorming last night and I think we should also introduce guard nodes.

So we have normal nodes (they just broadcast unverified POW/bounties)
Then we have super nodes who do the verification work and broadcast the verified POW/bounties
And then we have guard nodes who cross verify a certain percentage of the super node signed POW/bounties to detect malicious behavior

This way we do not even need to hard fork when we add new features / other work types later on since the supernode-signature-verification will remain the same!

I like the idea behind this. We can relate to science by calling those nodes "sentinel nodes" Wink