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
The following tests illustrate the problem, if you step through debugger you will see that it does not validate with coincurve and instead falls back to using the old validation with cryptography:
Investigate why old signatures created using
ecdsa
do not validate withcoincurve
:Old signing code (
private_key
in this case is instance ofecdsa.SigningKey
):lbry-sdk/lbry/wallet/transaction.py
Line 459 in 26d0e87
New signing code (calls the
libsecp256k1
code wrapped bycoincurve
):lbry-sdk/lbry/wallet/bip32.py
Lines 238 to 258 in 8076000
New validation code includes the old validation as fallback for old signatures:
lbry-sdk/lbry/wallet/transaction.py
Lines 428 to 440 in 8076000
The following tests illustrate the problem, if you step through debugger you will see that it does not validate with
coincurve
and instead falls back to using the old validation withcryptography
:Example 1 (older):
lbry-sdk/tests/unit/wallet/test_schema_signing.py
Line 74 in 8076000
Example 2 (much more recent):
lbry-sdk/tests/unit/wallet/test_schema_signing.py
Line 123 in 8076000
Why can't
coincurve
validate those signatures? Is there anything we can do to get it to validate?One interesting thing to note is that the new signatures do validate with the old validation scheme using
cryptography
library.The text was updated successfully, but these errors were encountered: