Rework felony.json

[frankcash]

Right now felony.json stores all keys added. This creates a problem since the User's private key is also stored in that file.

Some ways to go about this:

1. We need to think of a more secure way of storing the private key
2. not storing it and forcing the user to input it.

Definitely open to suggestions.

I could see this getting worked on with (#9)

[bugsysop]

Nice project, but not realy mature for massive use...

Some suggestions...

• Make keychain invisible: exemple .felony.json. It's not a good idea to have it exposed at the root of user home directory.
• Maybe separate public and private keys storage in separate files...
• Add backup(Feature Request - Backup private key #9) and import(Feature Request - Use Existing Keys #7) functions for private key in UI. This is missing...

[lakshayg]

How about encrypting the user's private key or the whole of felony.json with a master password which the user must provide every time?