Permalink
Browse files

Update README.md

  • Loading branch information...
johnshearing committed Nov 30, 2018
1 parent adb56ff commit 7caba1e8fbfcb4aadf0ff3d739134272198d1e8d
Showing with 1 addition and 1 deletion.
  1. +1 −1 Motivation/README.md
@@ -57,7 +57,7 @@ The PrivateKeyVault is meant to clear this bottleneck and make blockchain techno

Remember, the [PrivateKeyVault](https://github.com/johnshearing/PrivateKeyVault#privatekeyvault---click-for-open-source-make-instructions) is not a thing that someone is selling. It is rather a way of working that is freely accessible to anyone with electricity and an Internet connection. If we work together we can get everyone onto a public blockchain by sharing the [PrivateKeyVault GitHub repository](https://github.com/johnshearing/PrivateKeyVault#privatekeyvault---click-for-open-source-make-instructions).

**Second Big Problem Solve**
**Second Big Problem Solved**
**Private Keys Generated by Hardware Wallets are a Central Point of Attack**
The Nano Ledger and other similar devices use a pseudo random algorithm to generate private keys.
So if some [individual or government were to put a back door](https://www.wired.com/story/encryption-backdoors-shadow-brokers-vault-7-wannacry/) into the algorithm then everyone loses individual control of their accounts all at the same time. Avoiding this kind of disaster is the whole point of decentralization using blockchains. Individuals must have the right to generate their own private keys using a method known to be completely random. The private key is how an account is controlled. How can we hand this control over to any single entity?

0 comments on commit 7caba1e

Please sign in to comment.