jaimehgb

Yep, I've not published server side code :P Just what it's executed at the users' browser.

Nope, they are never sent to the backend. They are generated locally, ciphered with the password, and that ciphertext is sent to the server to be stored there.

Hmm yeah, not a priority but definitely yes :)

It's almost done too :P https://github.com/jaimehgb/RaiWebWallet/blob/master/js/custom.js#L1444 https://github.com/jaimehgb/RaiWebWallet/blob/master/wallet.php#L250 I was thinking on how to store its value, in a field near the wallet at the database or serialized with the wallet...

I haven't found a way to do that. The thing is that keys are decrypted at the browser with the user password, so when refreshing the page all data in...

That can be done. But then yeah, users will need to have 2 passwords. We can take an hybrid approach. Right now, when a user logs in, after decrypting the...

But for that you need 2 passwords. The way it works right now is: - Wallets are stored at the server encrypted. - User logs in with his identifier, gets...

It is encrypted with the rest of the wallet, with the main password. AES256 https://github.com/chriscohoat/rai-wallet/blob/master/src/Wallet.js#L1209

Pending Blocks (Waiting for PoW ...) is supposed to be there. It's wrong when blocks appear below and don't disappear in a few seconds.

Does it appear under the 'Pending Blocks' title? If it doesn't check if it appears in the transactions page and rebroadcast it with the paper plane button.