-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Improving account import #19
Comments
I started off using the Bouncy Castle Scrypt implementation, however migrated to the Java Scrypt library as per the following comments in the Wallet implementation. Note: we don't use the Bouncy Castle Scrypt implementation org.bouncycastle.crypto.generators.SCrypt, as the following parameter assertion results in failure of the Ethereum reference Scrypt test vector:
|
Oh I didn't know that, I used Bouncy Castle and I have never received that error because my test accounts have r = 8 and N = 262144. |
Closing, as for the time being I want to ensure that web3j remains compliant with the Scrypt test vector. |
I saw that you are using the Java Scrypt library to calculate the derived key.
I noticed that is not that fast and I found that the Bouncy Castle implementation is better.
Here is the class and method that you can call.
org.bouncycastle.crypto.generators.SCrypt.generate(...)
Hope this can improve the Web3j library.
The text was updated successfully, but these errors were encountered: