You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bip32 will be using the secp256k1 library on release (soon)... but I haven't yet finalized an ECC API that I am happy with in bitcoinjs-lib itself.
We want to move to secp256k1 before Christmas 😄 .
I like the idea of keeping the .sign() object function so that users can swap in whatever library they need with abstractions like TransactionBuilder etc.
But, in ECPair, with getAddress gone, the utility of the abtraction has dropped to near zero.
I don't want to pass a Buffer(Length: 32) private key to TransactionBuilder.prototype.sign though... so what should we do?
Where we can offer a easy-sauce secp256k1 compatible ECPair abstraction that provides .sign etc as available now, and then users who don't use that can simply do whatever they want, provided they return a 64-byte R|S encoded signature.
ecurve
is slow, but battle tested.Related #350
#623
#459
#508
#407
The text was updated successfully, but these errors were encountered: