Quote from: Jannn on August 03, 2016, 10:37:38 AM

Quote from: bitsec731 on August 02, 2016, 12:59:54 AM

First 2 consultations are free, so if you are not satisfied with my advices you can just give me negative reputation.

I can take a vouch.
Do it in public, to get your service started.

I have a paper wallet, printed offline with bitaddress.org. Advice me!

Alright here is my first impression analysis of Bitaddress and your setup:

1) Bitaddress.org

Vulnerability #1: Javascript is known to have bad RNG and all sorts of bugs that may or may not be patched. Especially browser based javascript is so bad, that I don't even keep up with it. They use window.SecureRandom instead of Math.Random() which is a custom CSPRNG library, little better but, I doubt it gives you really good security given the structure of the javascript language and the bloat from the browsers.

Vulnerability #2: If you use it with Chrome or other closed source browser, then its worse

2) Handling the private key

Did you generate the key offline on a safe machine? If not, then its a problem.
Did you securely wiped the hard-disk/flash memory after creating the private key? If not, then its a problem.
Did you securely wiped the wiped the printers memory after printing it out? If not, then its a problem.
Did you added extra encryption to the paper you printed out, in case a thief see's it and steals it? For example printing out an encrypted version of the key, so that even if somebody gets physical access to it, cannot decrypt it without password.

My advices:

Drop the javascript nonsense and generate the private key with electrum on an offline PC with linux on it. And wipe all persistent memory after done (ex: RAM, printer memory, hard disk, flash drive ,etc)

Consider at least steganography for paper wallets, hiding the private key inside pictures. Printing out trivial pictures that has your private key hidden it it, it less obvious for thiefs and easier to hide.

https://en.wikipedia.org/wiki/Steganography#Printed
http://www.jjtc.com/Security/stegtools.htm

We could go deeper, but these are my immediate advices.