wasm/webassembly bundle about nanocurrency-js HOT 5 CLOSED

• Yes, it's used for faster PoW computation
• It does have the WASM embedded. I don't think the limit is hit, yet. I consider rewriting the C code to AssemblyScript, so it would be a good time to think about it
• The output would be asm.js, not WASM

from nanocurrency-js.

@roccomuso Indeed, the 4KB limit is hit.
That's not a problem, though: computing a PoW takes time and blocks the thread, so it should not be used (and cannot because of the limit, anyway). The solution is to use Web Workers, as in the PoW benchmark example: https://marvinroger.github.io/nanocurrency-js/packages/nanocurrency/examples/pow-benchmark/

I am closing this as I know there's room for improvements when it comes to the WASM, but let's track this in #17

from nanocurrency-js.

Is computing PoW mandatory for a "lite wallet"? that just create, sign and broadcast a transaction? because at this point we can distinguish and in some case avoid the wasm bundle.

from nanocurrency-js.

No it's not. Just don't compute the PoW and put the work to null in the createBlock function.

The WASM is only loaded when calling computeWork. Also, with tree shaking, if you don't call it in your own code, the WASM won't be present in the final bundle.

from nanocurrency-js.

That's great!

from nanocurrency-js.