Skip to content

Bad single point of failure #25

@NickP005

Description

@NickP005

There is no way for the standard user to know
if the code they are running has been compromised or not. I suggest making a downloadable public client. The web code could be easily modifiable by the manager of the web server as hoc to all or to specific users (through ip or cookies) to reveal or obtain the private keys/vote.

Plus the system is not an open blockchain, but a closed one saved in MySQL I guess and there is no way of mining it/running it decentralised.
This is why I have decided to make a similar project but with various improvements (actually got the idea and started working on it way a long time ago, just found this and was going to stop working on my project but then realised this has big point of failure and there is still a big room for improvements).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions