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

consider detectability as a severity benchmark #126

Open
kristovatlas opened this issue Aug 19, 2016 · 0 comments
Open

consider detectability as a severity benchmark #126

kristovatlas opened this issue Aug 19, 2016 · 0 comments
Labels
Milestone

Comments

@kristovatlas
Copy link
Member

users who detect that an attack has taken place are more likely to take preventative measures to avoid them in the future. this arguably comes into play for blockchain and network observers in 2 ways:

  1. blockchain observation is silent, while active network observers (eg P2P Sybil attackers) are not. 2. There are arguably better open source / free tools available to point out privacy mistakes on the blockchain than there are for network-based problems, and so there is more demand for blockchain-based countermeasures.
@kristovatlas kristovatlas added this to the 3rd edition milestone Aug 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant