Quote from: kdrop22 on September 18, 2014, 01:34:23 AM

Can someone explain to me how this improves the security of GreenAddress. As I am new to BTChip and GreenAddress.

Process to use GreenAddress/BTChip
a) The GreenAddress seed is generated on the live machine.
b) I store a backup of the seed and notedown PIN
c) A copy of the seed is written to the BTChip
d) BTChip is able to sign transactions
e) However, the GreenAddress login can easily be done using the PIN. (without the need for a seed or BTChip). So, I assume the Green address seed is being stored somewhere on my PC.
f) Even if you were to use the BTChip for login. The mnemonic can be easily accessed from the Green address GUI, once the login is accomplished. If it can be accessed using the GUI, I assume the malware can access it as well.

e) the PIN is disabled if you create the account when using the card - and you can delete the PIN if you decide to onboard an existing account into the card, which solves the problem.

f) that part might be a bit confusing - you see the mnemonic on wallet creation, because it's not disabled right away, but you won't see it if you log in using BTChip after that.

Quote from: vitruvio on September 18, 2014, 05:51:56 AM

Then you can login with the btchip, if you lose the btchip you will lose all of course, for me it's easier to lose the btchip with my car keys than to lose a seed phase written in a paper and stored properly.

I'm not sure I get what you mean here - that might be because I don't drive, but you keep a seed backup in any case (whether the seed is generated by the GreenAddress client during setup, or generated by the dongle), that you can use if you lose the card - the point is that you never have to type the seed or the PIN into a potentially vulnerable computer again to log in or move funds.

Quote from: vitruvio on September 18, 2014, 05:51:56 AM

Nobody explain it but I think this works that way, if I'm wrong please ~~correct me~~ show me a user manual and then I won't have to suppose how.

the user manual is a bit lagging behind, we'll update the FAQ with specific BTChip security details soon