Skip to content
Raiblocks wallet source code
Branch: master
Clone or download
Latest commit 0abbaf1 Jan 30, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
assets Password managers dont break 2fa now Dec 21, 2017
img Pseudo initial commit Jul 12, 2017
js Complements the previous commit Jan 4, 2018
less Pseudo initial commit Jul 12, 2017
nacl Pseudo initial commit Jul 12, 2017
node_modules Pseudo initial commit Jul 12, 2017
Block.js Wallets can now be created from a backup (seed) Dec 8, 2017
Logger.js - Fixes stuck PoW Jul 14, 2017
Wallet.js Added a login key to notify the server when a wallet has been success… Jan 3, 2018
blake2b.js Pseudo initial commit Jul 12, 2017
common.js Pseudo initial commit Jul 12, 2017
functions.js Possibility to add labels to accounts Aug 5, 2017
pow.wasm PoW is computed client side on computers by default Dec 17, 2017




This is a web based wallet for RaiBlocks

This repo contains all the files which are downloaded to the browser at RaiWallet. Adding a compatible back-end anyone can build his own web based wallet from this.
The wallet itself is at Wallet.js. If you want to verify how blocks are created, signed and verified, how accounts are generated, etc ... you should look there. With it you can build your own private and homemade RaiBlocks wallet :D When an efficient way to generate PoW is found, the wallet will be almost self-sufficient. It will only need to query a server to get info about the ledger.

At js/custom.js you can find like the "Middleware" between the Wallet and the GUI. It also contains all the queries made to the server to request PoW, info about accounts and transactions, etc ...

The code relies on some NPM libraries for node.js. I've used browserify to use them at the browser.
$ browserify js/custom.js -o main.js (for example)

How is it built into

At RaiWallet the server is only used to store the users' wallets (ciphered), to provide information about the network to them, and to generate PoW. When a user signs up, a random identifier is generated to store the user wallet under it, but the wallet is created at the browser (seeds, keys, accounts, transactions, signatures, everything ... ). Once the user is done with the wallet, it is ciphered (AES256) with his password, still at the browser, and then the ciphered wallet is sent to the server to store it. Someone with access to the database wouldn't be able to find users' keys (if passwords are strong enough and haven't been leaked by their owners).


Any kind of help is appreciated :) Suggestions, proposals, fixes, TODO items, issues, testing ... If you want to help there is stuff to do :D


With the purpose of testing the wallet strength I have prepared a wallet with an account containing 2000 XRB as a bounty for the one able to log in to that wallet. The wallet has been created at, using the code in this repo. I can give you all the info you need, except the password. Im going to start providing you with the wallet identifier, the account, the password format (I would prefer you to break it in a way other than bruteforcing it :P but well ...), the ciphered wallet data and... yeah
If you need more info, just ask. If you find a vulnerability and it is worth it I may consider increasing the bounty. So yeah, lets play!

Wallet Identifier: 2964ae96e92370aee570aa92419bc3698dd611172acc2fc85781a43c29bcc9aa 
Account: xrb_3haojq7ntgd45qe1wde4bkqqruazt4sspw6r3ceshfqjnnrzaof63qhhehmf 
Bounty: 2000 XRB ---> 0.07 BTC --> 300$ (at time of writing, 2000 XRB will always stay the same)
Wallet Ciphertext Hex-encoded:


- Find an efficient way to generate PoW at the browser.
- Allow user to change pbkdf2 password stretching iterations (security).
- Allow user to set a minimum receive amount (Utility)
- Allow user to import a wallet seed, importing all chains in case it has been used already in the network (Utility)
- Allow user to import single private keys, of course not backed by the seed (Utility)
- Load more transactions when scrolling down the txs page, currently only the last 20 are loaded (UX)
- Change URI when changing tabs (UX)
- On page refresh, show up the login modal with the wallet id already filled so users can log back in quickly (UX)
- Intensive testing.
- Code cleaning.
- Client/Server comunication optimization, there are too many calls.
You can’t perform that action at this time.