New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 3 #48
Comments
I don't know what your goals are, so it's a bit hard to assess these proposals. From top of my head:
There is no
Depends on the Node versions you want to support. Personally I'd not use it.
What is the reasoning behind this? |
I suppose we could drop node
Simplification - I don't know if they are being used - if anyone feels otherwise we can keep them. |
Sure, I'm just saying that you can't expect
0.x is EOL and in between there was iojs :) So yeah, definitely drop everything < 4 https://github.com/nodejs/LTS
My company has a use case for mnemonic -> entropy, so I'd be happy if you keep it around 😁 |
@prayerslayer you probably should be using
@prayerslayer could you elaborate on why you use @fanatid I think we need to specify |
@dcousens sorry, I do not understand, what's wrong with Japanese wordlist? |
@fanatid it requires the |
agrh, I see... we can store seprator with wordlist... |
@prayerslayer could you elaborate on why you use Added a checkbox that we should change to an async API to support high performance AFAIK, only
Any thoughts on how we should? |
Any thoughts on how we should? |
{
separator: '...',
words: [...]
} ? |
@fanatid we will need to re-write the download script |
ping @prayerslayer ? |
@dcousens |
@oed was truncating the |
Right, now I remeber. There is no way to go from seed -> mnemonic. The reason I want this is because I want to split the entropy into multiple parts using shamirs secret sharing. Then I can give these parts to some delegates. When I recreate the entropy I want to be able to get the mnemonic again. |
@oed do you ever need (thanks for this information btw) |
I need both. In case a user want's to recover with mnemonic and then split this and give to delegates. |
See #74 |
mnemonicToSeedHex
, remove implicit hex support, Buffer onlysafe-buffer
mnemonicToEntropy
andentropyToMnemonic
from the public APIpbkdf2
, aka, anasync
API (Support high-performance PBKDF2 (async API) #72)Thoughts any/everyone?
The text was updated successfully, but these errors were encountered: