Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Minimal browser builds

See original GitHub issue

by supplying our own more minimal version of https://github.com/crypto-browserify/crypto-browserify we can drop the following deps:

require('diffie-hellman')
require('browserify-sign')
require('create-ecdh')
require('public-encrypt')

bc we are only using

crypto.randomBytes
crypto.pbkdf2Sync
crypto.createCipheriv
crypto.createDecipheriv

we just need to make a more minimal crypto entrypoint https://github.com/crypto-browserify/crypto-browserify/blob/master/index.js and sub it out with the browser field https://github.com/substack/node-browserify#browser-field

Issue Analytics

State:
Created 7 years ago
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

axiccommented, Dec 4, 2016

@tad88dev @hitchcott I’m afraid that is an intentional parameter of using scrypt. The point of scrypt is to be CPU and memory hard. Using the C scrypt implementation it is >10 times faster though.

In the browser it should be run in a worker.

Alternatively you can try tweaking the scrypt parameters (https://github.com/ethereumjs/ethereumjs-wallet#remarks-about-tov3) with the risk of reducing security significantly. Some wallets (such as keythereum) use much lower iteration count and thus they are faster. etheruemjs-wallet uses the default settings used by geth.

1reaction

IstoraMandiricommented, Dec 1, 2016

@tad88dev same experience; toV3 is taking around 20 seconds in Chromium