diff options
author | Kevin Cernekee <cernekee@gmail.com> | 2018-10-28 13:20:33 -0700 |
---|---|---|
committer | Kevin Cernekee <cernekee@gmail.com> | 2018-10-28 15:10:51 -0700 |
commit | 611f76238dedd0418c79a0d918d46d2c92b0149c (patch) | |
tree | 93ca072521fb19c304fe85764cfcb26387f918bd /src/css | |
parent | 011533e4bc1d49a6675dedf5bfaabefb7de41088 (diff) | |
download | BIP39-611f76238dedd0418c79a0d918d46d2c92b0149c.tar.gz BIP39-611f76238dedd0418c79a0d918d46d2c92b0149c.tar.zst BIP39-611f76238dedd0418c79a0d918d46d2c92b0149c.zip |
Allow converting mnemonic back to raw entropy value
Currently, this sequence produces an unexpected result:
1) Navigate to bip39-standalone.html
2) Paste a known-good mnemonic into the BIP39 Mnemonic field
3) Select "Show entropy details"
This will erase the BIP39 Mnemonic field and most of the derived
address/key information. It shows an empty Entropy field, and zeroes
for Event Count, Bits Per Event, Raw Entropy Words, Total Bits, etc.
However, it will show valid Word Indexes and BIP39 Seed.
The way to fix it is to convert the mnemonic back into a raw entropy
value and populate it in DOM.entropy, so that everything stays
consistent. This will only happen if the mnemonic is manually entered
by the user, not if phraseChanged() is triggered by hand-editing the
entropy value.
Diffstat (limited to 'src/css')
0 files changed, 0 insertions, 0 deletions