Jonathan Underwood

You can use tiny-secp256k1 v1 without schnorr support. For schnorr support, convince your bundlers to support WASM out of the box with 0 configuration.

correct. Those will not work. There's a pure JS implementation out there, but it uses Native JS BigInt, which is newer than WASM.

bip32 works with the latest tiny-secp256k1

React Native always lags behind on implementing every single standard API in JavaScript. Node has been much better with keeping up with browsers in recent years. The current tiny-secp256k1 will...

Last I checked there was a polyfill that enables WASM in RN. If you want schnorr, you'll have to look into that, or create a thin wrapper library around another...

@motorina0 this sounds like fun...

It seems like the only way to "fix" this is to remove node based hashing and only use pure JS hashing. Alternatively, we could also use WASM.

or actually this might be better fixed upstream: https://github.com/crypto-browserify/createHash

......? I looked at Node v17 API for createHash... it hasn't really changed... Is it just that OpenSSL no longer supports ripemd160?

Fixed in 3.1.0