Jonathan Underwood

tiny-secp256k1 uses RFC6979, which does not include any provably incorporated randomness. The e parameter is mentioned in the second bullet point in section 3.6 of RFC6979. https://datatracker.ietf.org/doc/html/rfc6979#section-3.6 However, there are...

The move to Rust+WASM will make it easier to implement if we have access to C libraries (using Rust FFI)

The biggest performance impact in your loop is `derive` as it performs ECDSA multiplication and addition which is expensive. My guess: When attached to debugger, you are using private xprv...

@DavidLiuBlockChainTech You should measure the time each line of HDNode.prototype.derive takes. It seems extremely obvious that derive is causing the problem... so you need to measure each step in there.

First, learn about bip32 with examples here: https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/bip32.spec.ts bip32 can be accessed by bitcoinjs.bip32 as well, no need to add as a dependency. Then pick a derivation scheme. BIP49 using...

good, except your getAddress function uses p2pkh which is BIP44. BIP49 must be p2sh-p2wpkh.

@pieterjandesmedt modified your code to use the correct address generation and testnet network for everything.

Working on it now. Starting with tiny-secp256k1. I am thinking of implementing TaggedHash and schnorr signing in tiny-secp256k1 itself since it is very bitcoin-specific. There is a PR currently up...

Hi @andrewtoth, thanks a lot. There are quite a few large things I need to work on in order to get this out. You helped a ton with # 3,...

I am against releasing a v6 with just the address changes. If you are really set on releasing the address change ASAP, add some new methods and revert the changes...