should be able in the user side, the browser be able to generate his keys based on his password

[xmonader]

flow should be: password -> make it in a specific length (fill with zeros) -> convert to mnemonic -> menmonic to seed -> get the public key, should be done in the client-side

libs to check

• bip39
• sodium wrappers
• tweetnacl

[abom]

The following is an example using tweetnacl and bip39

brnacl.zip

Used browserify with tweetnacl and bip39 (assuming they're installed):

browserify -r tweetnacl -s nacl > tweetnacl.browser.js
browserify -r bip39 -s bip39 \                                
 --exclude=./wordlists/japanese.json \
 --exclude=./wordlists/spanish.json \
 --exclude=./wordlists/italian.json \
 --exclude=./wordlists/french.json \
 --exclude=./wordlists/korean.json \
 --exclude=./wordlists/chinese_traditional.json \
 --exclude=./wordlists/chinese_simplified.json \
  > bip39.browser.js