-
Notifications
You must be signed in to change notification settings - Fork 0
Frequently asked questions (FAQ)
In our implementation, the ethereum nodes that compose the blockchain network will be held by the concerned departments of the Flemish government. In the future one could perfectly well imagine that accredited organisations or enterprises would run their own nodes.
Allowing anyone to run nodes or to have direct access to the network is counter-advised not only for privacy reasons, but also because nodes could modify data present on the blockchain.
The nodes don't represent anyone in particular, they are simply the network itself.
Our application implemented a middleware API as to enforce a private blockchain.
A private blockchain ensure that no personal data outside of their owns are accessible to the end-users.
Even using just hashes, would make it possible to retrieve personal information trough the links between those hashes.
Our project, and oSoc as a whole are pro-open source, believing that open source enhance significantly the value of our work. Indeed, open source is more secure, following Linus's law of "Many eyes make the bugs shallow" and more reusable as everyone can use parts of the code.
As such, we feel it important to let the users know how and why we store their data, including here.
Our team is positive that more knowledge about how personal data is handled can only result in more trust from the wider public. As such the woningpas project as a whole and the oSoc part of it should result in the citizens trusting more what data they have access to. Nonetheless, if a way to make the personal hashes stored on the blockchain available to the end-user while still ensuring privacy came to light, it should be implemented as soon as possible, as multiple members of our team feels that they would trust the information significantly more if it was the case.
The information on the blockchain is secure so long the majority of nodes (or whatever amount is needed for consensus) are not compromised. Any hack, so long it is noticed would be easily reversed by having the whole network go back to a block before the hack.
It depend on the consensus type, but all (including the one used by kaleido) but the computer intensive ones (like proof of work) should not consume such a massive amount of computer power to require anything beyond a normal server.