Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security Audit Needed #54

Open
gmkarl opened this issue Mar 7, 2016 · 5 comments
Open

Security Audit Needed #54

gmkarl opened this issue Mar 7, 2016 · 5 comments

Comments

@gmkarl
Copy link

gmkarl commented Mar 7, 2016

Since Qora was created, there have been a number of issues identified in the basic concept of the proof-of-stake blockchain. Other projects have found solutions to these issues, but most of these solutions have not been integrated into Qora.

Qora is in need of somebody experienced in proof-of-stake issues to bring it to the same level of security as the other chains. The development focus on features has provided incredible quality here, but there should be verification that Qora does not suffer from, for example, the simple nothing-at-stake issue.

@icreator
Copy link

icreator commented Mar 7, 2016

""projects have found solutions" - about what you say?
" nothing-at-stake issue" - in NEXT?? NEM?

@gmkarl
Copy link
Author

gmkarl commented Mar 7, 2016

https://en.wikipedia.org/wiki/Proof-of-stake#Criticism NXT ensures that forks will not happen below the top 720 blocks, so history older than 720 blocks cannot be changed via the nothing-at-stake issue.

NXT also has a great feature it calls "cumulative difficulty" which prevents forking of a long chain by an immature short chain.

Basically I am saying that Qora is in need of somebody to evaluate the PoS implementation and plug any possible well-understood issues in the PoS communities and report that they are plugged.

@osdio
Copy link

osdio commented Mar 8, 2016

+1

@icreator
Copy link

icreator commented Mar 8, 2016

in POS Coins: if new chain was created (hard fork) - it may kill first blockchain in any case!
This problem not solved in ALL POS coins and can not be solved

@gmkarl
Copy link
Author

gmkarl commented Mar 8, 2016

@icreator what are you talking about? that is not a serious issue in all major PoS chains

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants