Closed motorina0 closed 2 years ago
Signer and SignerAsync are interfaces that are being used in bitcoinjs-lib in Psbt etc... so adding more constraints would be a breaking change and we don't want to do that.
Right now, just leave those interfaces alone. Once proper taproot is supported, we will probably add a new interface for schnorr.
linter is failing... (tslint should exclude test files tbh)
Updated:
lint:tests
CI
flow tough, the issues it reported were not noisesignSchnorr()
from SignerAsync
Signer
since ECPairInterface extends Signer
README
dependencies
to latest
package-lock.json
Please remove signSchnorr
from Signer
as well. And add it to ECPairInterface
instead.
Please remove
signSchnorr
fromSigner
as well. And add it toECPairInterface
instead.
Done!
LGTM other than the README stuff.
LGTM other than the README stuff.
Great! README
file code sample fixed.
Thanks a ton. Published as 2.0.0
Closes: https://github.com/bitcoinjs/ecpair/issues/3
Summary
bip32
ecpair
fromtiny-secp256k1
ecc
lib must be provided by the consumer ofecpair
(see tests for details)TinySecp256k1Interface
interface only exposes the methods required byecpair
testecc.ts
checks the methos ofTinySecp256k1Interface
ECPair
is no longer directly exported, but insteadECPairInterface
is exposedsignSchnorr()
andverifySchnorr()
have been addedThe changes are split in 4 commits which can be cherry picked if needed.
Further comments
SignerAsync
is usedsignSchnorr()
- has been added to this interface