Where is the "p" in N, r, p?

Hey thanks for the lib!

How come there is no param for p in the usual scrypt N, r, p?

For example, from the node.js reference implementation:

scrypt.hashSync(key,{"N":16,"r":1,"p":1},64,"")

https://github.com/barrysteyn/node-scrypt#test-vector-1

Thanks!

[thinkloop]

The ethereum blockchain requires p be over 1 for certain values, and web workers will take a while for wide-spread support, there’s a nice little niche spot for single-threaded chunked variable p scrypt’ing. Just showing a case for demand, not asking for free work 😄. All the best.

On Wed, Jun 22, 2016 at 5:40 AM, Dmitry Chestnykh [e-mail] wrote:

Yeah, I’d like to implement parallelization parameter one day, but this will happen in a new library I’m currently writing (although I’ll probably accept a pull request). Here I just removed it for simplicity of implementation, as interrupted async loop is already crazy enough.

The thing is that each p is intended to load one CPU thread, so the proper implementation would use a web worker for each computation. (Although, even the reference implementation doesn’t implement parallelization yet!) However, if we have access to web workers, we don’t even need the complexity of scrypt-async, we can just make scrypt synchronous and put the whole scrypt computation into a web worker.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dchest/scrypt-async-js/issues/22#issuecomment-227693991, or mute the thread https://github.com/notifications/unsubscribe/AAHQHnT6eSQzjhdwgybUofwE1EJHku7Vks5qOQMmgaJpZM4HmUft .

[dchest]

Yeah, I’d like to implement parallelization parameter one day, but this will most likely happen in a new library I’m currently writing (although I’ll probably accept a pull request). Here I just removed it for simplicity of implementation, as interrupted async loop is already crazy enough.

The thing is that each p is intended to load one CPU thread, so the proper implementation would use a web worker for each computation. (Although, even the reference implementation doesn’t implement parallelization yet!) However, if we have access to web workers, we don’t even need the complexity of scrypt-async, we can just make scrypt synchronous and put the whole scrypt computation into a web worker.