How can client side enforce one time setting of sendmoney public key?
API v2 won't have sendMoney. Client soft will prepare transaction and sign it locally. Then the transaction will be broadcasted. This is 100% secure if client provides 100% security.
Just landed in paraguay.
Api v2!
Ok so in api v1 it is impossible to add second layer of security, but in api v2 it is possible to add second layer.
Was this the original plan? I guess it doesn't matter, the important thing is we now have a roadmap to 256bit ^ 2 security. Clearly with api v1 biggest threat is from weak user passwords, tainted downloads, key loggers and user errors.
The thing that really bothered me about v1 security was that there was nothing i could do to prevent the offline cracking of password, remote as the chance is, i want to be able to reduce almost zero chance to almost zero chance twice, especially if i will have most of my net worth in the nxt acct!
The fact that there is no parallel attack for the second password means that fragmented wallet will eliminate temptation of hacker who stumbles onto nxt password.
With v2 i will be able to bring in super large investors. Thank you for supporting my "unreasonable" request
James
